What is the EARS methodology used in this skill?

EARS (Easy Approach to Requirements Syntax) is a system for writing requirements using five specific templates (Ubiquitous, Event-Driven, State-Driven, Conditional, and Optional) to ensure they are unambiguous and testable.

What happens after the design phase is complete?

Once the design is approved, the skill transitions to the spec-driven-implementation phase, which breaks the design down into TDD-based tasks for execution.

How does the research phase work?

The skill uses WebSearch and WebFetch tools to look up best practices, API documentation, and prior art related to your feature, documenting findings in a Research Summary before requirements are finalized.

Can I use this for existing features or only new ones?

While optimized for new features, you can use the /dev-workflow:spec commands to document or redesign existing features by pointing the skill to your current feature directories.

Spec-Driven Planning

Name: Spec-Driven Planning
Author: xbklairith

byxbklairith

•

Productivity & Workflow

Guides feature planning through a systematic three-phase workflow encompassing structure creation, EARS requirements engineering, and architectural design.

About

Spec-Driven Planning is a professional-grade workflow skill that transforms vague feature ideas into rigorous technical specifications. By following a structured path from directory setup to EARS (Easy Approach to Requirements Syntax) elicitation and architectural trade-off analysis, it ensures that developers have a clear, documented roadmap before writing a single line of implementation code. It leverages automated research and deep-thinking protocols to validate technical approaches and identify edge cases early in the lifecycle.

Key Features

EARS methodology implementation for clear, testable, and unambiguous requirement syntax.
UltraThink integration for deep reasoning on complex scalability and security challenges.
Three-phase automated workflow: Feature Creation, EARS Requirements, and Technical Design.
Architectural trade-off analysis with comparative options and complexity estimations.
Integrated Research Protocol to analyze prior art, competitor APIs, and technical standards.
1 GitHub stars

Use Cases

Defining rigorous requirements for complex enterprise features to prevent scope creep.
Evaluating multiple architectural approaches for a new service before starting development.
Bootstrapping new project modules with standardized documentation and task structures.

About

Key Features

EARS methodology implementation for clear, testable, and unambiguous requirement syntax.
UltraThink integration for deep reasoning on complex scalability and security challenges.
Three-phase automated workflow: Feature Creation, EARS Requirements, and Technical Design.
Architectural trade-off analysis with comparative options and complexity estimations.
Integrated Research Protocol to analyze prior art, competitor APIs, and technical standards.
1 GitHub stars

Use Cases

Defining rigorous requirements for complex enterprise features to prevent scope creep.
Evaluating multiple architectural approaches for a new service before starting development.
Bootstrapping new project modules with standardized documentation and task structures.