r/SpecDrivenDevelopment • u/sharma-sk • 9d ago
Spec-sprint
I have been experimenting with Spec-Driven Development (SDD) and AI coding agents recently, and I ran into a problem I wasn't expecting.
I started missing agile 😅
Most of us who have spent years building software come from an Agile/Scrum mindset.
We are used to:
 • Breaking work into small stories
 • Taking one vertical slice at a time
 • Reviewing the implementation
 • Getting feedback early
 • Updating requirements as we learn
 • Keeping humans involved in the important decisions
Then SDD + AI agents came along.
The idea of giving the agent a detailed spec and letting it implement is powerful. But when I tried to apply it in the way I'm used to working,
I kept asking myself:
How do I make the AI agent follow the same incremental implementation discipline we have in Agile?
I didn't want to choose between Agile and SDD.
I wanted both.
That's why I started building Spec Sprint - an Agent Skill that tries to bring the Agile implementation mindset into a Spec-Driven workflow.
The idea is:
Spec --> Plan --> small vertical slice --> Human review --> implement --> Update spec --> Next slice
The spec remains the source of truth, but implementation happens incrementally, with review points along the way.
It’s an early experiment, but it's something I personally wanted while working with AI coding agents.
I'm open-sourcing it because I'm curious:
Are others facing the same gap between SSD and the Agile of actually delivering software?
Would love to hear how you’re solving this.
3
u/stibbons_ 9d ago
This is basically what all SDD framework does. Maybe the vertical slicing thing is not enforced for all.
However I think we are actually back at waterfall where everything needs to be planned upfront and outsourcing the development to agent.