Spec-driven development isn't waterfall with markdown. It's not a productivity trap. It's also not a silver bullet. The honest version is more useful than either the evangelist or the cynic gets credit for — and it's why your AI coding agent stops shipping the wrong thing.
The pages below assume the prior ones were read. The arc runs from the ground up: why SDD exists, how to author your first spec, how it compares to practices you already know, how to choose a framework, and how to run it solo. Specs are half the picture: a spec is the stop condition, and a loop is what keeps running until it's met — see loop engineering. Want a full spec to build an agent yourself? See the free agent specs library.
Hitting the prompting wall, hearing about SDD, deciding if it is hype.
Anatomy, sizing, acceptance criteria, mindset, substrate, lifecycle, longevity.
Orienting SDD against TDD, RFC, and PRD — practices you already know.
Landscape, multi-framework comparisons, head-to-heads, decision tree.
Agent stack, solo workflow, reviewing AI-generated PRs without a teammate.
Connect your repo. Twelve loops start watching your code and bring you proposals — you greenlight them, your coding agent builds them.