spec-driven

Specification-driven development (SDD) uses natural language specifications as the source of truth for software development. By enforcing a mandatory workflow of specifying, clarifying, planning, and implementing features, it prevents scope creep and ambiguous requirements.

To implement a new feature, begin with the Specify phase to define requirements in natural language. Then progress sequentially through Clarify, Plan, Tasks, and Implement phases to ensure code directly serves the documented specifications.

Yes, specification-driven development supports TDD workflows by structuring implementation plans and task breakdowns before coding. It ensures that data models and feature specs are clearly documented, providing a testable path from concept to final implementation.

The best way to structure implementation plans is using a structured documentation methodology that separates planning into distinct Plan and Tasks phases. This ensures feature specs and data models are broken down into actionable tasks aligned with business intent.

You should not use specification-driven development for rapid prototyping or exploratory coding where requirements are completely unknown. It enforces a rigorous 5-step workflow that requires clear natural language specifications before any implementation begins.