spec-driven-dev

Spec-driven development is a structured workflow that enforces plan-first coding by requiring clear specs, design validation, and task-driven implementation. It reduces ambiguity and rework through a four-phase process with mandatory phase gates and approvals.

To enforce design review before coding, implement a four-phase workflow with phase gates that block implementation until a formal design review is approved. This ensures no coding begins before design artifacts are validated and signed off.

To sequence implementation tasks, generate a tasks.md artifact after design approval that breaks down work into atomic commits. Ensure each task has a specific verification command before implementation begins to maintain controlled progression.

Yes, phase gates are suitable for cross-functional teams that need explicit planning before coding. The workflow spans product, design, and engineering roles by requiring approved requirements and design artifacts before implementation begins.

Spec-driven development should not be used for simple tasks that skip the need for formal specs, design artifacts, and task sequencing. It is designed specifically for complex features requiring controlled PR-based implementation and cross-functional alignment.

Spec-driven development requires verification commands for each task to ensure atomic commits are validated before progression. This controlled PR-based implementation step guarantees that every sequenced task meets its specific acceptance criteria.