spec-driven-planning

Spec-driven planning generates a feature skeleton and captures requirements using EARS templates. Run `/dev-workflow:spec create` to start feature creation, then `/dev-workflow:spec requirements` to define Event-Driven, State-Driven, and other requirement types in a structured format.

EARS (Event Analysis and Response Specification) structures requirements by event triggers and system responses. Use it during requirements capture to make implicit feature behaviors explicit and testable, reducing ambiguity in feature specifications.

Yes. Spec-driven planning covers feature creation, requirements gathering, and technical design phases. It provides design templates and guides you from initial requirements through detailed technical artifacts stored in organized directories.

Spec-driven planning creates a feature skeleton with ready-to-use design outlines, EARS-based requirement documents, and technical design artifacts. It organizes these as templated documentation stored in structured directories for your project.

No. Spec-driven planning uses templates and guided workflows to structure your planning process. The templates handle the format; you focus on defining requirements and design decisions for your specific feature.