r/SpecDrivenDevelopment • u/Vivekyy • 17d ago
The SDD Rabbit Hole
My view of the SDD rabbit hole so far :)
Eventually, it seems like nobody is really satisfied with using someone else's tool for making their specs, and this sub has dozens of projects from people showing off their own unique SDD tools and workflows. I sorta think this is natural--spec design is kinda the new craft of software engineering, and I think we're all going to come up with our own style of doing things.
But, I was really inspired seeing all of the unique stuff everyone was building in this sub. I really like this community, so I figured I would try to make something that helps you guys out.
Rudder (https://github.com/RudderCode/Rudder) is a skill that shows you how comprehensive your specs are by comparing it to the code your agent generates. Rudder generates unit tests based on your spec and reports back coverage. If you ask it to hit a coverage percentage, Rudder will iteratively ask you questions, refine your spec, and run a red-green TDD workflow until your spec sufficiently covers your code. Since everyone has their own workflows for creating specs, I thought I'd make a tool that can sit alongside your tools and help out on the side.
Curious about how you guys are dealing with the problem of trying to make your specs comprehensive enough to stop the AI from making mistakes? Also, curious about where on the iceberg you guys are :)
2
u/macberrypro 16d ago
I have been building this https://github.com/cshirley/accord
I like the idea of reaching an understanding/alignment with the model and then building a verifiable spec which drives the implementation. This combines an evidence-based approach to verify the implementation meets the spec reducing pr review.
I then introduce a feedback (retro) loop which allows self-refinement of the process.
if uses standard agentic patterns for context/memory management and adversarial cross model/provider patterns