r/SpecDrivenDevelopment • u/No_Article_5669 • 40m ago
TeDDy: a coding harness for iterative, incremental development
r/SpecDrivenDevelopment • u/No_Article_5669 • 40m ago
r/SpecDrivenDevelopment • u/ditomax • 5h ago
Getting a first version running with Claude Code is quick. The trouble starts months later, when something has to change and nobody, the agent included, knows what the code was meant to do.
build is one answer to that: a free, open-source skillset (MIT). Concept documents are the specification and the code is derived from them. My test is whether a second agent could rebuild the product from the documents alone.
You type "start", then "next", "redo" or "stop". A director skill runs four stage skills:
A human decides at three gates: requirements, consistency findings, and a gap analysis before release.
Also built in: STPA-light (losses, hazards, constraints, each traced to a requirement and a test) and secret protection before the first line of code (hook, gitleaks pre-commit).
Plain markdown, nothing to install. Open the folder in Claude Code, Codex or Cowork and type "start", or symlink skills/build* into ~/.claude/skills/. Customer-specific rules go into a profile/ folder instead of a fork.
Repo: https://github.com/ditomax/build
Actually tested on two projects, medical app and a skill for fault detection in electrical installations in factories.
For those maintaining agent-written code longer than a few weeks: where does drift show up first for you? Does spec-first hold up, or does it just move the problem into the docs?
r/SpecDrivenDevelopment • u/protayne • 2d ago
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?
r/SpecDrivenDevelopment • u/JinxedBluejay • 2d ago
Hi. I had no idea there was a community for this. I've been doing the spec driven development for a while and am in the process of making an IDE specifically for this use case... by using this method.
I guess I'll just leave a link here and let you guys take a look at it.
I didn't want to post in the vibe coding subs because I'll be honest they seem kinda... lazy.
Anyways... This is the basics, my github page and the project page explain more:
Every non-trivial task proceeds through gates, and every gate follows the same loop:
Orchestrator writes a self-contained prompt
│
▼
Fresh Qwen session ── reads AGENTS.md ── does ONE step ── writes evidence files ── "STOPPING AND WAITING"
│
▼
Orchestrator audits the tree and the evidence ──► PASS | PASS WITH NOTES | FAIL
│ │ │
│ fix loop (same session) │ corrective prompt
▼ │
I commit the gate, commit the updated docs, push ◄──────────────────┘Several properties of this loop are deliberate:
AGENTS.md first.r/SpecDrivenDevelopment • u/migaloper • 2d ago
r/SpecDrivenDevelopment • u/simasch • 4d ago
Who here is actually building business applications for companies?
I have the impression that most posts are from solo developers.
r/SpecDrivenDevelopment • u/RetoricEuphoric • 4d ago
r/SpecDrivenDevelopment • u/PilgrimofHaqq2 • 5d ago
I was running several primary agents in parallel across multiple projects and the notifications were burying me. Every agent stopped to ask me something: "X or Y?", "found a side issue, fix now or later?" etc. I had become the bottleneck. my AGENTS.md cover many conventions/rules/standards but its still wasn't enough to cover so many of these questions.
So I restructured my workflow like a team:
How lanes work
lead.md file in the project plus the project's docs, and it has to cite the rule it used. If no rule covers the question, or it's a taste/preference call, it escalates to me.I still have full control
Every lane is a normal chat. I can open any of them, read the whole transcript, and type into it directly if I want to step in. The harness never merges a branch, deletes a branch, or removes a worktree on its own.
My notifications are now mostly things that actually need me. It's still early, and I keep refining what goes into lead.md, since that file decides how much the lead can handle without me.
So far I have noticed I am getting a lot more done with less headaches. (literally!)
r/SpecDrivenDevelopment • u/Verdict-Systems-NS • 6d ago
r/SpecDrivenDevelopment • u/psychobarge • 7d ago
r/SpecDrivenDevelopment • u/Pablito_3733 • 7d ago
r/SpecDrivenDevelopment • u/NiklasEldberger • 8d ago
r/SpecDrivenDevelopment • u/Sad-CTO • 9d ago
Hey guys,
I was talking to a friend the other day regarding how you should approach spec work and realized that I am thinking about it in a declarative way while the rest of the world seems to be thinking imperatively.
In a nutshell, chances are that if you want to, say, "add the email function to the product", you would think about this as a sequence of tasks: your flavor of of spec, dev, qa, deploy. From my perspective, tasks are secondary, a derivative, of a diff between two product states.
The current state is whatever is in production now, and its spec. The target state is the product with the email sending functions live. The diff is added/changed/removed spec items. The tasks are derived, because you can always reconstruct the tasks from the spec diff, but not vice versa.
There's more on this in an article on our website (link in comments).
LMK your thoughts, happy to discuss.
r/SpecDrivenDevelopment • u/afanasyevsanya • 9d ago
r/SpecDrivenDevelopment • u/mrasu27 • 10d ago
I'm developing a tool to check whether code satisfies formal specifications written in FizzBee. While TLA+ or FizzBee are good tools for checking whether a system can reach invalid states, they don't provide a way to verify implementations conform to the specifications. Unlike unit testing, there is no widely acceppted way to check implemented code follows a formal specification.
So, I built Spec Guardian:
https://github.com/mrasu/spec-guardian
It generates tests from the execution results of specifications written in FizzBee. The tests compare FizzBee's abstract states with concrete states stored in RDB tables or KVS. AI can also generate tests for the same purpose, but it tends to writes tests that follows implementations rather than specifications. That's why Spec Guarding generates tests primarily from FizzBee's results and yaml configuration.
Using Spec Guardian, I tested iceberg-go against a specification written by Jack Vanlightly.
As a result, I found that iceberg-go doesn't support Merge-On-Read mode and creates a single bundled file instead of multiple files as an optimization. While the goal of Spec Guardian is to find bugs, I think finding differences between implementations and specifications is a good sign that I'm on the right track.
It's still under development.
What do you think of this approach to comparing specifications and implementations? Could it become a new kind of AI harness? What features would you like to see added?
r/SpecDrivenDevelopment • u/Virtual-Laugh3386 • 10d ago
r/SpecDrivenDevelopment • u/engelschall • 11d ago
We released version 2.0 of Agentic Software Engineering ( ASE, https://ase.tools ), the Apache-2.0-licensed Open-Source toolkit that fuses the concepts of modern Agentic AI and traditional Software Engineering. ASE 2.0 ( https://ase.tools/news/#ase-2.0 ) delivers an agentic software specification and development approach. For this, ASE 2.0 integrates a new AI-driven task grilling mechanism and the brand new Specification Book ( SpecBook, https://specbook.tools ) companion toolkit. This way, ASE 2.0 supports Spec-Driven Development (SDD) based on both User Stories and Spec-as-Source. Additionally, ASE 2.0 now allows to realize SDD through agentic development pipelines where humans and agents closely cooperate on tasks.

ASE ships as a plugin for the agent harness Anthropic Claude Code CLI -- and with reduced functionality also for Github Copilot CLI and OpenAI Codex CLI. It comprises deeply integrated agent hooks and "mods", highly parameterisable agent skills, an underlying Model-Context-Protocol (MCP) backing service, a companion Command-Line Interface (CLI), and companion Terminal and Web User Interfaces.
r/SpecDrivenDevelopment • u/oppid • 12d ago
Hi everyone! I've been building pi-maestro, a Pi extension for a spec-driven multiagent workflow, inspired by GitHub Spec Kit and OpenSpec. It helps you define a change, clarify requirements, and approve a spec with concrete acceptance criteria. You can use it in two ways:
By default, three agents run in sequence:
You can disable the verifier and simplifier independently, using just the builder or pairing it with either agent. See phase configuration for details.
You make the scope decisions and review the final code.
I'd love some feedback, especially on whether the separation of roles is useful and where the workflow adds unnecessary friction.
If you've built something similar in Pi, I'd be interested in comparing approaches.
https://github.com/emilioSp/pi-maestro
If you find it useful, consider giving it a star on GitHub!
Cheers!
r/SpecDrivenDevelopment • u/Legal-Cattle-6224 • 13d ago
Most of the UI in our codebases is now written with an agent in the loop, and agents don't read Storybook. I wrote up what I changed in how I build a design system because of that: one contract per component feeding docs, types, a linter and an MCP server; events that follow platform rules; validation before review.
How are your teams handling this? Docs written for agents, codegen context, nothing yet?
r/SpecDrivenDevelopment • u/EnreachEnterprises • 13d ago
Most dev teams are finding that pure prompt-and-pray coding leads to messy, unmaintainable codebases.
The real shift in 2026? Spec-driven development.
When we build web automation tools at Enreach Enterprises, we don't just chat with an AI and hope for the best. We write clean structural specs first, let the AI handle the boilerplate, and use human judgment for architecture and security.
Speed is great, but code integrity wins enterprise trust. How is your team balancing AI velocity with quality control?
#VibeCoding #SoftwareDevelopment #TechTrends #AIAutomation
r/SpecDrivenDevelopment • u/Due_Warthog749 • 16d ago
r/SpecDrivenDevelopment • u/naxmax2019 • 16d ago
I've always believed in that specs should be detailed and validated. So I created ideavalidator as a mod and skill. It's here: https://github.com/alinaqi/ideavalidator
Here's how it works:
It's a grounded idea-validation pipeline..
The target isn't "a good idea": it's a business that's profitable from day one. Two principles rule everything:
- Desk research is never validation. Grounded research can at most justify GO → real-world tests (interviews, pre-sales, paid pilots), never GO → build.
- Behaviour beats stated intent. Money paid, workarounds built, tools switched > "I'd use this." Every evidence item is labelled so you can see which kind it is.
How you start it
- From a URL: ingest --url <site> [--idea "<angle>"] reads the site + search and writes ideas/<slug>.md.
- From an interview: the skill asks only for the missing brief fields (actor, job, workaround + cost, why-us, candidate verticals, money, business model, day-one constraints).
- Then: run --idea ideas/<slug>.md executes the pipeline into runs/<slug>/.
Here is what makes it more than a prompt chain:
The output can be used with any coding agent to convert into todos and actual implementation or the idea can be killed.
Hope it helps.
PS: it was part of my agentic superharness palgu.ai and I decided to opensource it.
r/SpecDrivenDevelopment • u/pmz • 17d ago
Under spec driven development,how does a developer design the UI layout, elements as well as their on screen ordering the way he wants, when he doesn't touch the code? is the design specified somewhere and then referenced from the specs?
I know that something like that is being done with Figma, but what about when using templates like HTML+Thymleaf?
To sum it up, does the Agent do as it thinks when desiging layouts or do you instruct it, and how? Some practical references or examples would be useful. Thanks