Member-only story
Stop Writing Specs. Start Writing Facts. The Entire SDD Movement Is Already Obsolete.
One test survived Sonnet 3.5, 3.7, 4, and Opus 4.5+. The spec needed four reinterpretations.
“A theory that explains everything explains nothing.” — Karl Popper, philosopher of science
Six times over the past months I’ve written on Medium that Spec-Driven Development is the answer to vibe coding chaos — today I’m walking back the first part of that sentence, only the first part, and I’ve got data for this movement that you won’t be able to ignore.
If you’re currently rolling out Spec Kit, Kiro, OpenSpec, or BMAD to production and your CI has quietly started chasing Claude model upgrades every few weeks, the problem isn’t on your end — the fundamental assumption behind these tools is cracking under the weight of non-deterministic systems, and Google Trends shows the movement started declining two months ago, from a peak of 100 in March to 86 in May.
In the next ten minutes you’ll see why one executable test, written in June 2025, has passed CI without modification through Sonnet 3.5, 3.7, 4, and Opus 4.5+ to this day, while a 1,500-word specification describing the same endpoint required four reinterpretations — and how to migrate CI from Spec-Kit-heavy to…
