[!todo] Seed note. A starting point, not a finished note yet.
Spec-driven development puts a precise specification (behavior, interfaces, acceptance criteria) upstream of implementation, so the code is generated against a stated contract and the reviewer checks the diff against that contract instead of guessing why it exists. It matters most in an AI workflow: the dominant cost of code review is reconstructing intent, not reading syntax, and AI floods review with more and larger changes whose intent is opaque. A shared spec converts that reconstruction cost into a check against something written down, which is why it functions as a way to elevate the review constraint rather than just add reviewers. Related to [private link] and Definition of Done. Seeded from AI SDLC Bottleneck.