spec-driven-development

Turn vague requirements into approved, testable specs.

software development

What it does

Guides development from a structured specification through validated planning, tasks, and implementation.

When to use it

Use for substantial projects, features, architectural decisions, or work with ambiguous requirements or multiple affected modules.

Give it a development goal; it works with you through human-reviewed specification, planning, task, and implementation phases in the project.

No additional actions listed in the analysis.

Requires planning-and-task-breakdown as the canonical source for implementation planning and task breakdown.

Requires incremental-implementation while executing implementation tasks.

Requires test-driven-development while executing implementation tasks.

Requires context-engineering to load relevant specification sections and source files during implementation.