@PawelHuryn: Spec-Driven Development was always BS. It never worked for humans. Waterfall lost to agile because you discover what yo…
Summary
This tweet argues that Spec-Driven Development is ineffective for AI agents, drawing parallels to the failure of waterfall methodology in software development. It advocates for 'intent engineering'—communicating context, strategy, and constraints to agents to handle unknown unknowns.
View Cached Full Text
Cached at: 07/04/26, 04:50 PM
Spec-Driven Development was always BS.
It never worked for humans. Waterfall lost to agile because you discover what you actually need while building, not in a spec written up front. Thariq’s field guide is the clearest proof it’s the same for agents: the unknowns surface during the work and after it.
The fix isn’t hunting down every unknown unknown either. It’s communicating the context beyond the goal, the why and the strategy and the constraints, so the agent navigates the unknowns you never listed.
I’ve been calling this intent engineering since January. Agents don’t fail because the model is weak. They fail because the intent is incomplete.
Similar Articles
@GergelyOrosz: Both AWS’s Kiro and GitHub Workflows was built on the idea of spec-driven development (you or the agent writes a spec f…
A tweet discusses why spec-driven development, as used in AWS Kiro and GitHub Workflows, failed to gain traction, referencing an analysis by @dexhorthy.
@zachlloydtweets: https://x.com/zachlloydtweets/status/2071670840660533393
Zach Lloyd details how to build a spec-driven development agent within a cloud software factory, using triage and spec agents to handle ambiguous or complex issues by generating product and tech specs before implementation.
Engineering discipline
A developer discusses the challenge of maintaining engineering discipline and architectural integrity when using AI coding agents that generate code faster than it can be comprehended, seeking best practices to avoid creating low-quality software.
Are coding agents exposing how bad our specs actually are?
The article argues that many failures of AI coding agents stem from vague specifications, not just model weaknesses. It suggests that writing clearer, more detailed work packets may be the next essential skill for developers using coding agents.
Why giving AI coding agents architectural context in text is fundamentally broken
AI coding agents struggle with implicit architectural decisions when given text descriptions. The author built specrabbit, a visual canvas for defining architecture as typed nodes and flows to export a machine-readable spec.