Chapter 01
The three files
Separate WHAT and WHY, HOW, and STEPS across requirements.md, design.md, and tasks.md.
ENGINEERING · GUIDE
Spec-Driven Development
How to build features through requirements → design → tasks
A practical seven-page guide to taking a feature through requirements.md, design.md, and tasks.md with tests, checkpoints, and one source of truth.
- Author
- Mykhailo Markhain
- Edition
- Version 1
- Format
- 7-page PDF
Inside the guide
A spec that helps teams ship features faster.
A practical route from an approved product brief to reviewed, checkpointed implementation.
Chapter 02
The delivery flow
Connect the product brief, refinement, technical review, tickets, build, and release to the spec.
Chapter 03
Operating principles
Keep the spec as the source of truth without adding another approval stage.
Chapter 04
Requirements without invention
Check every requirement and acceptance criterion against the approved product brief.
Chapter 05
Design and cost assessment
Record architecture, data model, API contract, and production-scale risks before coding.
Chapter 06
Tasks and implementation
Work task by task: tests, code, commits, and full-suite checks at every checkpoint.
Chapter 07
A worked example
See the three artifacts applied to a realistic feature from requirements through release.
The core idea
The spec is the source of truth.
Every non-trivial feature lives in its own folder: requirements.md captures WHAT and WHY, design.md captures HOW, and tasks.md captures the ordered STEPS. Checkboxes and commits make progress visible without another status meeting.
spec-driven developmentSDDDripifyrequirements.mddesign.mdtasks.md