spec-driven-development

Spec-driven development generates structured specifications and implementation plans from feature descriptions. Use the specify command with your feature description, then plan to define technology stack, producing spec.md, plan.md, data-model.md, and tasks.md artifacts that guide development from requirements through execution.

Yes. This workflow generates independently executable user stories and decomposes features into granular tasks within a standalone environment. It produces task.md with actionable items and corresponding implementation scaffolds, enabling development without external dependency management.

The four-stage workflow moves from specify (WHAT/WHY) through plan (technology stack and architecture), tasks (decomposition), to implement (starter code). Each stage generates documented artifacts, creating a traceable path from initial concept to ready-to-develop implementation templates.

Yes. The plan stage accepts technology stack input and generates architecture decisions, data-model.md, and structured implementation guidance. It supports defining frameworks, databases, and component relationships before writing production code.

Spec-driven development applies to both new projects and incremental features. It generates complete specification and planning artifacts independently, making it suitable for greenfield projects, feature branches, or architectural planning at any project stage.

The specification-first workflow produces spec.md (requirements), plan.md (architecture), data-model.md (schema and entities), tasks.md (decomposed work items), and implementation starter scaffolds—all generated without external dependencies.