Understanding Spec-Driven-Development: Kiro, Spec-Kit, and Tessl
3 comments
·October 16, 2025yodon
gsadaka
I have also struggled to find real world examples for these approaches.
Following a BDD approach with a coding CLI works a lot better, as it documents the features as code rather than verbose markdown files no one will read.
Having a checklist for an AI to follow makes sense, but that's why agents.md exists. Once the coding patterns and NFRs are documented in it, the agent follows them as well as they would follow a separate markdown spec.
iamdeedubs
In my experiments with SpecKit I was always left wondering "when does it merge all this specs into a single ground truth". I never got there and it felt like a huge missing step.
Now I'm left trying to define/design what a "spec" for communication between humans and coding agents would look like, to power what Birgitta called spec anchored.
This pretty much aligns with my experience with SpecKit - I'm excited by it, and enjoying working with it, but have had a hard time finding guidance on advanced real world use cases.
All the tutorials I've found are little more than "here's how to install it - now let's make a todo list app from scratch!!"
Would be great to see how others are handling real world use cases like making incremental improvements or refactorings to a huge legacy code base that didn't start out as a spec driven development hello world project.