@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
@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.
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.
@arcane_bloom: The Shift from Software Engineering to Agent Engineering: A 5-Part Breakdown 1/6 Most developers fail when building AI …
A thread explaining the 5 core mental shifts needed to transition from traditional software engineering to agent engineering, emphasizing why conventional patterns like hard-coded routes and binary tests fail with AI agents.
People who write specs for AI coding agents?
The article discusses varying approaches to writing specifications for AI coding agents and asks for community input on effective methods.
@zachlloydtweets: https://x.com/zachlloydtweets/status/2065154860337508577
The article outlines a five-step workflow for spec-driven development using Warp skills: write a product spec (PRODUCT.md), write a tech spec (TECH.md), implement with any AI agent, validate implementation matches specs, and validate using computer use with Oz. The skills are open-sourced and can be installed via npx.