r/SpecDrivenDevelopment • u/protayne • 1d ago
I can't be the only one concerned that we're becoming so focused on how quickly AI can produce code that we're forgetting all these learnings we've had from decades of SWE...
I've been following the growing popularity of SDD, doing it myself, I can't help feeling we're overlooking engineering practices we've spent decades developing and shouting about.
It's very common to see workflows where an AI agent writes a markdown spec, implements code, then writes tests to validate the same implementation. Huge PRs and reduced human review.
I know some SDD kits support test-first development, but doesn't seem to be the default approach.
A Markdown specification can't go RED or GREEN on its own. And tests passing doesn't necessarily mean you've built the right thing.
I've seen discussions around removing humans from PR reviews entirely, which I find a bit mad. Why not instead automatically flag changes to agreed business behaviour, contracts or fitness functions as requiring particular human attention, but then again not many teams are in a position where they have these...
Is anyone making use of SDD in such a way, following the classic workflows of TDD, BDD, FFDD and ATDD?
I've been working on this tool to help combat this and having good results, so this is also a shameless plug, alongside wanting to hear from proponents of SDD.
The main principle is:
AI may propose and implement changes, but it must not independently redefine the conditions by which those changes are judged successful.
It's still very much an early alpha, built by just me. Currently Windows x64, .NET 10, ASP.NET Core APIs and Reqnroll/MSTest. The packaged release supports Codex, with Claude Code and Cursor support being developed.
I've started benchmarking against Spec Kit too, with some promising early results, although there's a lot more work needed there.
Repo: https://github.com/tayzer/TADA
I'm not against SDD at all. Quite the opposite, I think there's a lot of potential here. I just worry we're so focused on the speed of AI-generated code that we're overlooking some of the lessons we've learned from decades of software engineering.
I'd genuinely love some criticism from people using SDD regularly. Are you already incorporating executable acceptance tests into your workflows? How are you stopping agents from modifying their own success criteria? And is requiring human approval of those criteria too much friction?
