Putting Spec Kit Through Its Paces: Radical Idea or Reinvented Waterfall?

This title could be clearer and more informative.Try out Clickbait Shieldfor free (5 uses left this month).

Spec-Driven Development (SDD) proposes using detailed specifications as the source of truth for AI agents to generate code. Testing this approach with Spec Kit on a real feature rebuild revealed significant drawbacks: excessive markdown generation (2,500+ lines), long agent execution times (33+ minutes), and 3.5 hours of review overhead. Traditional iterative prompting proved 10x faster, completing the same work in 8 minutes of agent time with minimal review. The workflow felt like a return to waterfall methodology, producing duplicative documentation without improving code quality or reducing bugs. While SDD presents interesting ideas worth discussing, the practical implementation through Spec Kit doesn't capitalize on AI's strength of making code cheap and fast to produce.

18m read timeFrom blog.scottlogic.com
Post cover image
Table of contents
What is Spec Driven Development (SDD)?Pick a framework …The challengeGetting startedConstitutionSpecifyPlanTasksImplementationNext incrementSpec Kit Process OverviewComparing my ‘regular’ approachA Critique of SDDCode is the lawA return to waterfall?It didn’t result in better code or fewer bugsAre agents better at writing markdown or code?Is SDD teaching agents to suck eggs?In defence of SDDParting thoughts
1 Comment

Sort: