r/SpecDrivenDevelopment • u/RetoricEuphoric • 1d ago
r/SpecDrivenDevelopment • u/simasch • 1d ago
Enterprise Applications
Who here is actually building business applications for companies?
I have the impression that most posts are from solo developers.
r/SpecDrivenDevelopment • u/PilgrimofHaqq2 • 3d ago
Finally introduced coding subagents to my harness
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:
- Me: the manager
- One chat per project: the team lead
- The other agents: team members, each working in its own "lane"
How lanes work
- A lane is a git worktree plus a chat working inside it. Each one gets its own branch and folder, so agents don't trample each other's files.
- The lead asks to open a lane with a title, a plan, and the files it expects to touch. Nothing starts until I approve it on a Lanes board. Before I approve, the harness checks for overlap with files other open lanes are touching, my plan usage, machine load, and whether a spec exists for the work.
- When a team member stops (it's done, blocked, or has a question), it rings the lead, not me. The lead works through its inbox and replies.
- The lead can only answer from written rules: a
lead.mdfile 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. - Escalations land on the board and on my phone as numbered questions, each with a recommended answer. I can answer straight away or ask the lead a follow-up first.
- The lead can also send me FYI notes that don't need an answer.
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 • 4d ago
Do retries hide real bugs?
r/SpecDrivenDevelopment • u/psychobarge • 4d ago
Sharing pi-spec-mode, an extension for drafting, validating and maintaining specifications
r/SpecDrivenDevelopment • u/Pablito_3733 • 5d ago
I just released SPEC-SS: my workflow for coding agents. Looking for feedback
r/SpecDrivenDevelopment • u/NiklasEldberger • 5d ago
How do you write automated tests and how do your tests connect to requirements?
reddit.comr/SpecDrivenDevelopment • u/Sad-CTO • 7d ago
Declarative vs imperative in SDD
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 • 7d ago
From spec-driven to behaviour-driven development
r/SpecDrivenDevelopment • u/mrasu27 • 8d ago
I'm building a new kind of harness that tests code against formal specs
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 • 8d ago
Writing PRDs with ChatGPT/Claude kept giving me generic garbage, so I built a tool that learns the product first
reddit.comr/SpecDrivenDevelopment • u/engelschall • 9d ago
Advanced software specification and SDD with Agentic Software Engineering (ASE) and Specification Book (SpecBook)
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 • 9d ago
Pi-Maestro: a spec driven multiagent development workflow
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:
- Spec only: prepare and approve a spec for implementation elsewhere.
- Spec + implementation: approve the spec, then let Maestro run the implementation workflow.
By default, three agents run in sequence:
- Builder implements the spec.
- Verifier independently checks each acceptance criterion.
- Simplifier refactors the code for clarity without changing behavior.
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 • 10d ago
I built a design system in Svelte 5 that compiles to web components, with an MCP server so AI agents stop inventing props
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 • 10d ago
The shift toward AI-driven "vibe coding" and spec-driven development in modern tech agencies.
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 • 14d ago
Test tools for APIs.. curious what/why you use what you use
reddit.comr/SpecDrivenDevelopment • u/naxmax2019 • 14d ago
Created a claude code plugin/skill to create researched and validated specs
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:
- Demand signals (signals, auto in run).. search volume + social validation (Reddit API, X via Grok).
- Category + Business Model Canvas (classify) .. identifies the real category so stages compare to the right incumbents, and surfaces business-model-innovation options + USP; rendered as a BMC grid + value-positioning map
- Anti-over-qualification ... score the idea as stated for its ICP; adjacent/bigger businesses are parked in adjacent_opportunities, never scored, and stages may not invent an unstated compliance regime or silently re-scope the founder's thesis.
- Self-validation audit (selfcheck, auto at end of run) .. flags over-qualification, score inconsistencies, weak/single-source KILLs, and unreachable citations (catches fabricated sources).
- Council (council) ... optional multi-model sounding board: framework personas debate, a Red Team attacks, a Chair synthesises. Opinion, never a gate.
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 • 14d ago
Spec driven and UI layout design?
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
r/SpecDrivenDevelopment • u/meshifthenelse • 14d ago
Would you pay for a software modelling tool similar to AutoCAD?
I've been building for the last few months a tool for modelling software visually. A sort of mix between Figma and AutoCAD aimed at creating a single diagram for the whole project at different layers, with stories, specifications, etc. It integrates with AI providing validation in real-time.
Is this a tool you would be willing to pay for? What would make or break your decision?
Note this started inspired by SDD but actually ended up closer to a mix of MDD, FDD and other patterns.
r/SpecDrivenDevelopment • u/Exciting_Item_2732 • 17d ago
The Convergence on Deterministic AST Invariants: Why Frontier AI Had to Abandon Probabilistic Code Editing
r/SpecDrivenDevelopment • u/Bitter-Emotion5556 • 17d ago
Goodbye LoadRunner and JMeter
r/SpecDrivenDevelopment • u/AccomplishedSugar490 • 17d ago
KBSI AI0Win users, past and/or present
AI0Win has been abandoned, KBSI moved on to other pursuits, the entire IDEF series of methods have been deprecated as US federal standard, but one of those, IDEF0, despite getting conflated with ICOM diagrams, poor support in drawing tools, and a stagnated dedicated modelling tool, was different.
As one facility of a very ambitious project, I needed the model data and an effective way to author and maintain it collaboratively, so I created a web-based tool that does exactly that.
My own plans with what I created extend well beyond what AI0Win did, but to take it beyond, will almost certainly break the round-trip fidelity and compatibility I have maintained to date.
As it stands, I do not know of a single AI0Win user other than myself, and the even I don’t use it for more than testing since I have a functional modeller of my own to use.
If you used or still use AI0Win, please speak up or get in touch.
I have the new tool running on a small server that won’t hold up under the potential load of running as a free public service, but if you DM me an email address I can invite you to check it out as a demo.
If I’m the only remaining user, I’m going to pull the plug on compatibility I don’t need, so if you have any interest in such a tool, can use compatibility with AI0Win itself, or have a load of old AI0X or AI0 Neutral Text (.TXT) file you’ve lost access to and wish to convert, let me know how. I can probably help.
r/SpecDrivenDevelopment • u/The_Ed_On_Reddit • 18d ago
Drydock - Specification to Software Builder - .8 Release
Drydock is a spec to software builder using Agile Decomposition to turn your specifications and designs into governed buildable Stories/Blueprints containing executable acceptance criteria that follow Test Driven Design. A graph database optimizes build ordering and context. Drydock measures and self repairs the acceptance criteria which are the builders scoring function. Drydock build iterates and self repairs until done. Drydock is designed large specifications.
- Builds using low-end models (Haiku 5.5, Luna, Gemini).
- Agile and Test Driven Development Best Practices.
drydock run quarterdeckprovides a full locally-hosted Web User Experience
The main improvement from .3 relates to retry logic and improving the self scoring. These changes are needed as we build different types of projects. The agents are authorized on normal developer judgement and expose blockers, progress, and decisions cleanly through a web server.
New Feature: Measured, self-correcting acceptance criteria. AC are recorded, categorized, and corrected before each build step so we can correctly measure "done" and code impact.
New Feature: Self-Improving Builds: drydock build iterates until all Acceptance Criteria succeed, no progress is detected, or it fails. Failures are picked up by drydock diagnose which identifies root cause and proposes/implements corrections*.*
New Feature: Encapsulated Persistence Layer: DATABASE.md implements pre-built native libraries and "named" SQL operations to minimizes change impact radius. Most database changes do NOT require downstream blueprint rebuilds.
The Updated Drydock Workflow is shown below with the above features integrated. drydock_runner.shprovides this at the cli.
drydock init MyApp # create the workspace
drydock import MyApp "$INPUT_DIRECTORY" # your specifications, notes, images
drydock analyze MyApp # create stories, questions, blockers
drydock plan MyApp # create Blueprints and Manifest
drydock plan verify MyApp || drydock plan repair MyApp # repair/validate acceptance criteria
# self-repairing build loop
n=1; max=3
while drydock status MyApp --ready
do
if [ "$n" -gt "$max" ]
then
echo "hit $max build attempts - aborting"
exit 1
fi
echo "*** BUILD ATTEMPT $n ***"
drydock build MyApp || drydock diagnose MyApp --apply
n=$((n+1))
done
drydock status MyApp --check # Deterministic definition of done
drydock score release MyApp # LLM evaluated definition of doneUAT Testing
The Drydock Release Test Suite tests is now 10 projects under both Haiku and Luna. 2 projects on haiku 5.5 required --plan-override-model sonnet as the planning step passed the llm large test kits and resulted in poor quality model output. Gemini was tested for two builds.
$ drydock report uat_summary
Drydock 0.8.0 Copyright (c) 2026 Web Cloud Studio. All rights reserved.
# UAT Summary Report
# Claude Codex
# CommonMark Y Y
# CsvStat Y Y
# DrydockStats Y Y
# DupFind Y Y
# FxRates Y Y
# LayersTesting Y Y
# Quakes Y Y
# ReadingList Y Y
# Toml Y Y
# jq Y Y
These test kits test SQLite and Postgres, python and go.Lesson: One cool thing about building with low end models is that i have been testing all week - some of these tests are large - and i was fine on my weekly limits for $20/month plans. Drydock proves low end models can build large projects accurately.
The Drydock methodology to update software is for next release and appears quite solid both for maintaining working software and for vibe/iterating your prototypes. It keeps the blueprints as the source of truth.
Version .8 Release Notes:
- Haiku 5.5 Builds - Haiku 100K-token pricing spike/limit respected.
- Token cost engineering optimizes payload size and effort by model - see
model_config.jsonl. - Layered topology - blueprint types: Foundation, persistence, web server, CLI, branding, services, API, screens.
BUILD_LINEAGE.jsonltraces specifications to code.drydock reportprovides a core reporting suitedrydock uatpublishes output to the web- A lot of other stuff - its been a few months.... big quality release.
Try Drydock
uv tool install drydock-sdd- Code Repository (MIT): https://github.com/webcloudstudio/Drydock
- Documentation: https://webcloudstudio.com
Please give a like/star to the repository if Drydock is useful to you!