Six months of SDD discourse summarized: the "three-month wall" is real, the tooling is fragmenting fast, and nobody has solved brownfield yet

Six months of SDD discourse summarized: the "three-month wall" is real, the tooling is fragmenting fast, and nobody has solved brownfield yet


We pulled together roughly 30 sources — HN threads, practitioner guides, tool documentation, and a handful of recorded case studies — covering spec-driven development (SDD) as it's evolved from late 2025 into early 2026. Some of what we found was predictable. Some wasn't.


**The pattern that keeps coming up**


GitClear data, cited across multiple independent sources, puts AI-driven code duplication at 8x the pre-AI baseline. That number gets used to explain what practitioners started calling the "three-month wall": vibe coding gets you to a working prototype fast, but somewhere between months 4 and 9 you're in integration hell. Months 10–15, you're debugging architectural decisions nobody remembers making. By month 16–18, the codebase is stalled.


This isn't a fringe complaint. The same arc — fast start, slow degradation — showed up in nearly every source that tried to explain 
*why*
 anyone would adopt the overhead of spec-driven tooling in the first place.


**What's actually being built**


GitHub Spec Kit crossed 72,000 GitHub stars. BMAD-METHOD hit 46,200 at v6.6.0 (released April 29, 2026). AWS launched Kiro, an IDE built around SDD concepts — which is the first time a major cloud vendor has committed to the methodology as a first-class product. DeepLearning.AI shipped a dedicated course on spec-driven development with coding agents in late 2025.


What's striking is the speed of institutionalization. Andrej Karpathy — who coined "vibe coding" — publicly said in early 2026 that "the vibe coding era is ending." That's not a detached observer; that's the person whose framing launched the original wave.


**Does it actually work?**


The most concrete practitioner case in the corpus: a developer built Trainlytics, a real fitness-tracking app, in 4.5 hours using Claude Code and GitHub Spec Kit. The claimed discipline was keeping specs as the source of truth, specifically preventing agents from pushing fixes before updating documentation. One data point, clearly — but it at least names the exact tool and gives a time.


The canonical workflow that most sources converge on is four phases: Specify → Plan → Tasks → Implement. The spec is treated as the source of truth; the code is treated as a derived artifact. Most of the tooling (GitHub Spec Kit, OpenSpec, BMAD-METHOD) is built around enforcing that sequence.


**The open problems worth paying attention to**


Semcheck (rejot-dev/semcheck) is the most documented CI tool for spec conformance checking. Its creator built it using its own SDD workflow and found it identified real issues in itself once functional — which is a good sign. But there's a documented problem: the tool generates false positives when the model draws on its own world knowledge rather than the spec. Interestingly, O3 thinking models don't improve this. Claude 4 and GPT-4.1 apparently outperform O3 for conformance checking, which cuts against the usual assumption that more reasoning steps help.


The brownfield question is just open. OpenSpec claims brownfield support and targets exactly that use case with its `.openspec` folder approach. GitHub Spec Kit uses rigid phase gates that seem better suited to greenfield. But there's no controlled comparison in the corpus showing SDD working at scale on a real existing codebase of 10,000+ lines. The "it works on legacy code too" claim is asserted everywhere and demonstrated nowhere.


**The disagreement that won't resolve cleanly**


An HN thread on an InfoWorld piece (#48028876) had a commenter ("absynth") push back on the entire SDD-vs-vibe-coding framing: "Why not both? Dilemmas aren't necessary. Not everything is binary." That position has some weight. A few sources propose a hybrid tiered model — stay loose for exploration, formalize specs only when complexity demands it. But practitioners running actual teams seem to think the disciplines are incompatible in practice, not just in theory.


The tooling landscape isn't helping. GitHub Spec Kit, AWS Kiro, OpenSpec, BMAD-METHOD, GSD, RALPH-LOOP, VibeSpec, Semcheck, and CodePlain's `plain` language all compete in the same space with no dominant standard. That fragmentation makes team adoption decisions genuinely difficult right now.


One thing that did converge across sources: the bottleneck isn't AI capability anymore. It's spec quality. "The output of your code is only as good as the input of your specifications" showed up in multiple independent sources. Whether you find that reassuring or concerning probably depends on how much you trust your team's ability to write precise requirements.


Anyone in  or adjacent communities running SDD in production right now? Curious what tooling has actually stuck past the greenfield stage.


tl;dr — SDD is moving fast from hobbyist practice to vendor-backed infrastructure, but the brownfield problem and spec conformance tooling still have real gaps.Six months of SDD discourse summarized: the "three-month wall" is real, the tooling is fragmenting fast, and nobody has solved brownfield yet


We pulled together roughly 30 sources — HN threads, practitioner guides, tool documentation, and a handful of recorded case studies — covering spec-driven development (SDD) as it's evolved from late 2025 into early 2026. Some of what we found was predictable. Some wasn't.


**The pattern that keeps coming up**


GitClear data, cited across multiple independent sources, puts AI-driven code duplication at 8x the pre-AI baseline. That number gets used to explain what practitioners started calling the "three-month wall": vibe coding gets you to a working prototype fast, but somewhere between months 4 and 9 you're in integration hell. Months 10–15, you're debugging architectural decisions nobody remembers making. By month 16–18, the codebase is stalled.


This isn't a fringe complaint. The same arc — fast start, slow degradation — showed up in nearly every source that tried to explain *why* anyone would adopt the overhead of spec-driven tooling in the first place.


**What's actually being built**


GitHub Spec Kit crossed 72,000 GitHub stars. BMAD-METHOD hit 46,200 at v6.6.0 (released April 29, 2026). AWS launched Kiro, an IDE built around SDD concepts — which is the first time a major cloud vendor has committed to the methodology as a first-class product. DeepLearning.AI shipped a dedicated course on spec-driven development with coding agents in late 2025.


What's striking is the speed of institutionalization. Andrej Karpathy — who coined "vibe coding" — publicly said in early 2026 that "the vibe coding era is ending." That's not a detached observer; that's the person whose framing launched the original wave.


**Does it actually work?**


The most concrete practitioner case in the corpus: a developer built Trainlytics, a real fitness-tracking app, in 4.5 hours using Claude Code and GitHub Spec Kit. The claimed discipline was keeping specs as the source of truth, specifically preventing agents from pushing fixes before updating documentation. One data point, clearly — but it at least names the exact tool and gives a time.


The canonical workflow that most sources converge on is four phases: Specify → Plan → Tasks → Implement. The spec is treated as the source of truth; the code is treated as a derived artifact. Most of the tooling (GitHub Spec Kit, OpenSpec, BMAD-METHOD) is built around enforcing that sequence.


**The open problems worth paying attention to**


Semcheck (rejot-dev/semcheck) is the most documented CI tool for spec conformance checking. Its creator built it using its own SDD workflow and found it identified real issues in itself once functional — which is a good sign. But there's a documented problem: the tool generates false positives when the model draws on its own world knowledge rather than the spec. Interestingly, O3 thinking models don't improve this. Claude 4 and GPT-4.1 apparently outperform O3 for conformance checking, which cuts against the usual assumption that more reasoning steps help.


The brownfield question is just open. OpenSpec claims brownfield support and targets exactly that use case with its `.openspec` folder approach. GitHub Spec Kit uses rigid phase gates that seem better suited to greenfield. But there's no controlled comparison in the corpus showing SDD working at scale on a real existing codebase of 10,000+ lines. The "it works on legacy code too" claim is asserted everywhere and demonstrated nowhere.


**The disagreement that won't resolve cleanly**


An HN thread on an InfoWorld piece (#48028876) had a commenter ("absynth") push back on the entire SDD-vs-vibe-coding framing: "Why not both? Dilemmas aren't necessary. Not everything is binary." That position has some weight. A few sources propose a hybrid tiered model — stay loose for exploration, formalize specs only when complexity demands it. But practitioners running actual teams seem to think the disciplines are incompatible in practice, not just in theory.


The tooling landscape isn't helping. GitHub Spec Kit, AWS Kiro, OpenSpec, BMAD-METHOD, GSD, RALPH-LOOP, VibeSpec, Semcheck, and CodePlain's `plain` language all compete in the same space with no dominant standard. That fragmentation makes team adoption decisions genuinely difficult right now.


One thing that did converge across sources: the bottleneck isn't AI capability anymore. It's spec quality. "The output of your code is only as good as the input of your specifications" showed up in multiple independent sources. Whether you find that reassuring or concerning probably depends on how much you trust your team's ability to write precise requirements.


Anyone in  or adjacent communities running SDD in production right now? Curious what tooling has actually stuck past the greenfield stage.


tl;dr — SDD is moving fast from hobbyist practice to vendor-backed infrastructure, but the brownfield problem and spec conformance tooling still have real gaps.


#SDD #Speka #Web2Bizz #spec_driven #spec_driven_develop