Kiro, Spec-kit, Bmad, Tessl, and other SDD frameworks turn business analysts into Markdown reviewers. Isn't there a more agile way to use Coding Agents?

marmelab

Spec-Driven Development frameworks like Kiro and Spec-kit generate extensive Markdown documentation before coding, echoing Waterfall methodology. While promising structure for AI coding agents, this approach creates context blindness, excessive documentation review, and diminishing returns on large codebases. The author argues for Natural Language Development instead: an iterative, Agile-inspired approach where developers give coding agents simple, incremental instructions without formal specifications, enabling faster convergence toward working products.

Spec-Driven Development: The Waterfall Strikes Back

Spec driven development often fails because you can’t anticipate all requirements up front, key solutions and necessary changes often only become clear during implementation.

Upvoting for the Star Wars reference.
Loved this: &quot;Spec-Driven Development seems born from the minds of CS graduates who know their project management textbooks by heart and dream of removing developers from the loop. I think it’s a missed opportunity to use coding agents to empower a new breed of developers, those who use natural language and build software iteratively.
Let me end with an analogy: coding agents are like the invention of the combustion engine. Spec-Driven Development keeps them confined to locomotives, when we should be building cars, planes, and everything in between. Oh, and just like combustion engines, we should use coding agents sparingly if we care about the environment.&quot;

Agile doesn’t mean coding without specifications. Just iterating over small enough chunks.
All agile frameworks rely on:
<ul>
<li>User stories</li>
<li>Acceptance criteria</li>
<li>Definition of Done</li>
<li>Backlog refinement</li>
<li>Iteration planning</li>
</ul>
I am using Spec-kit fits really well in this iterative process.
As to the “Markdown madness” the author mentions, I love markdown docs. “The Code Is The Documentation” approach only for smaller projects, and projects you won’t get back after 2 years.

“I’ve successfully used coding agents to build fairly complex software without ever looking at the code”
That sentence tells me everything I need to know about the author, and it’s not a good thing. You really should look up the difference between vibe coding and vibe engineering.

“How do we remove developers from software development?” :-D love it!
I agree with this guy, I’ve started to use the same approach intuitively, because I want to control my code.