Spec-Driven Development

No code without a spec. The spec is both the blueprint for the work and the manual for the result.

Cycle

1. Spec — describe what needs to be built as a task in a spec file (docs/specs/*.md)
2. Build — implement the task
3. Document — after the task is done:
   • Mark the task [x] and add **Implemented:** bullets inside the task body
   • Update the feature description above # Tasks based on what was implemented

Spec structure

Each spec file has two parts:

1. Feature description (top) — what the product does, how to use it
2. Task journal (bottom) — starts with # Tasks; story groups under it use ## headings