addy-spec-driven-development

Write a spec covering six areas: objective, commands, project structure, code style, testing strategy, and boundaries. Surface assumptions explicitly, reframe vague requirements into testable success criteria, and get human approval before implementation begins.

Spec-driven development is a gated workflow with four phases: Specify, Plan, Tasks, and Implement. Each phase requires human review before advancing, ensuring the specification remains the shared source of truth between the engineer and stakeholders.

Skip the spec for single-line fixes, typo corrections, or changes where requirements are unambiguous and self-contained. Simple tasks still benefit from a two-line spec with acceptance criteria, but full specs are unnecessary overhead for trivial changes.

Create a capability map when one requirement bundles several independently testable capabilities. Define stable kebab-case module ids, one-directional dependencies with no cycles, and a build order, then write a separate spec per module in dependency order.

Code without a spec relies on unstated assumptions about requirements, architecture, and success criteria. A 15-minute spec surfaces misunderstandings before implementation, preventing hours of debugging and rewriting misaligned features.