
Spec-Driven Development Has a Rubber-Stamp Problem
Spec-Driven Development was supposed to fix vibe coding's core problem. But its safety mechanism, a human reviewing the generated spec, is exactly where automation bias kicks in. A more complete spec doesn't protect you from that. It makes it worse.

Spec-Driven Development: What It Is and Why AI Makes It Non-Negotiable
Spec-Driven Development isn't a new idea. What changed: AI makes the spec executable. It's no longer a document that guides humans - it's a command that drives agents.

Coding Agents are the sloppiest developers you'll ever hire
A coding agent doesn't fill spec gaps the way an experienced developer does. It exploits them. The difference isn't capability - it's consequence. This is a 2AM postmortem, and what it actually tells you about building with AI.

Spec-driven development starts one step too late
SDD tools like GitHub Spec Kit and AWS Kiro solve a real problem. But every one of them starts with a spec already in hand - and nobody asks how it got there.
