SDD Trends & Community Demand
A unified read of 44 SDD videos, issue trackers, comments, and articles: what the field says and what builders actually request.
The headline: the field stopped arguing about whether to write specs and started arguing about how to keep the AI honest — did we agree what to build (interrogation), did a second opinion check it (adversarial review), how do we know it's done (verification / evals). And the single loudest audience request, everywhere, is "support my tool."
Both point the same way: Companion's job isn't to add ceremony — it's to be the cross-provider layer that surfaces a few high-value gates and stays out of the way otherwise. The evidence below is one-sided on this.
Merges two passes: the 44-video trends report and the audience-demand study (GitHub issues, YouTube comments, ~35 Medium articles — debriefed in full here). Every source is clickable in the appendix.
Cross-provider is the category's #1 unmet need
🔥 dominantreinforces + edgeEvery rival's issue tracker is flooded with "support MY tool." Companion already does this by design — lead with it.
evidence
Spec Kit — Cursor CLI, Warp, Antigravity, Codex; BMAD — OpenCode (41 comments), Augment (31), Warp; OpenSpec — Zed, generic .agents installer; Superpowers — Antigravity, Gemini CLI, Hermes harness. On YouTube, the whole Sonnet-5-vs-Opus comment war is the same instinct.
2a · The AI should interrogate you first
🔥reinforcesLet the model interview you in multiple-choice rounds until the spec has no holes. The most common pattern in the videos.
evidence
Gui Ferreira's whole talk, Matt Pocock's "grill me," Spec Kit's /clarify, OpenSpec's "explore," Jellypod's 30-question write-plan — everyone converges on a recommended default per question and "keep going until complete."
grill-me recipe (W3·4). Persist the Q&A as a trace artifact, not just a spec edit. Ships as embedded prompt text; maps onto a webview wizard.2b · A different model should review the plan
🔥reinforces + edge"A model reviewing its own plan is an echo chamber." The most Companion-native idea in the whole corpus.
evidence
The grill-me + Codex talk caught real bugs by handing the plan to a second model; OpenSpec's adversarial authoring; Waldemar's separate validator.
2c · "Done" must be verified, not self-reported
🔥gap to closeKent Beck's "finger guns": the AI fakes "done." Don't auto-complete on its say-so.
evidence
Kent Beck (the AI rationalizes "11 of 19 tests pass" as done); Waldemar's "never let the agent judge itself"; Anthropic's self-verification frontier. Audience echo: "orchestration is just YOLO with better visuals." New GitHub signal: BMAD "excessive noise / AI slop in generated code".
mark-complete is a status promotion. Gate it on a tool-returned pass or a second-model verdict, and surface the AI's silent "judgment calls" for confirmation. Bridges the verifier recipe to the terminal node.2d · Evals — and the "is SDD obsolete?" debate
🔥new + contentThe hottest article thread lands directly on evals: facts / BDD / IDSD all say the durable artifact is an executable check.
evidence
Kapil Ahuja: SDD collapses on upstream change → IDSD/ICE. Wasowski: "write facts, not specs" + "BDD is the missing link." Falk Gottlob's rebuttal: "kill both — the prototype is the spec, the eval is the acceptance test." Every voice converges on executable acceptance criteria. Full debrief: the Medium articles.
3a · Brownfield, spec-editing & drift
🔥reinforces + gapSpec Kit's #1 issue is literally "can't edit existing specs." Brownfield is where the field is going — and Companion's biggest gap.
evidence
Spec Kit — Can't Easily Update or Refine Existing Specs, post-implementation debugging; OpenSpec — /opsx:repair, hierarchical specs, multi-repo/monorepo. Articles: Wasowski's "spec that survives code generation," Breunig's "keeping the triangle in sync."
/analyze drift/repair gate, codebase reverse-engineering for adoption.3b · Context durability — the trace as memory
🔥reinforces core"Context rot" is the cross-cutting enemy. Companion's trace is a context-durability layer on top of Spec Kit.
evidence
The showdown slots Spec Kit as the "spec layer," GSD as the "context layer"; context rot runs through Rick Hightower, Kapil (ICE), Wasowski, Goecke. Anthropic's managed agents keep an append-only log independent of the executor — a near-exact mirror of Companion's trace.
.spec-context.json as adding context survival on top of Spec Kit. Steal: capture decisions/rationale (the why), not just status, and re-inject on resume.3c · Governance / "approve intent, not code"
▲ risingreinforces + competitiveAdoption is settled; governance is the new bottleneck. Companion's gates + trace are the oversight surface.
evidence
Papalini: governance is the bottleneck once AI writes specs; the 2026-2030 forecast predicts devs shift to approving intent (and cites the study where they were 19% slower while feeling faster).
3d · Autonomy / loops / "builds while you sleep"
▲ risingreinforcesAuto-mode demand: cmux "hands-off," "24/7 agents," Papalini's "loop engineering."
evidence
Papalini's "Loop Engineering Is SDD in Motion"; YouTube's cmux, "Skills + Hermes = 24/7 agents," "Agentic OS."
3e · Anti-lock-in / artifact portability
▲ emergingcompetitive + contentLock-in relocated up the stack. Companion's plain-file trace is an anti-lock-in selling point.
evidence
Kapil's "Five Dependency Layers" (lock-in moves to your spec format/toolchain) and "SDD will collapse on upstream change."
Agent teams, worktrees, parallel implementations
▲ risingreinforcesFork the spec into parallel implementations and run agent teams — a top request across repos.
evidence
Den Delimarsky's worktree "multi-armed bandit." Demand: Superpowers' top open issue Agent Teams (21 comments), BMAD agent teams, Spec Kit multi-agent + spawn-worktree.
Fast-path default, gray-box plans, model routing
▬ steadyreinforces + newCredible voices warn against ceremony; "plans over-specify" is a real complaint. Validates lean-by-default.
evidence
"Less is more — 99% just use the baseline," "GSD without ceremony," "it looks like waterfall." Demand: Superpowers' plans over-specify, no room for executor judgment (17 comments). New GitHub signal — model-specific prompt brittleness: Superpowers "Sonnet 5 doesn't like the instructions", OpenSpec "Opus 4.6 skips the step".
Should Companion add evals? Yes — as a trend-watching layer, not a pass/fail gate. An eval isn't a unit test: judge scores are fuzzy and never settle (the speaker's own drifted 94/96/100 with no code change), so you watch the trend. "A single score can lie to you. A trend is much harder to fool."
mechanics
- Eval = cases + scorers. The spec's acceptance criteria are the cases — they already exist.
- Two scorer kinds, both in reach: deterministic code scorers (structural + a tool-call assertion: did the agent call the right command with the right params? — maps onto verifying Companion's own dispatch); and an LLM-as-judge that must be a different model, blind to who wrote the answer — exactly what cross-provider enables.
- Store history, diff against a baseline — the value is the delta across re-runs.
- Already half-built: the bench harness has an LLM judge (
behavioral-judge) + scorecard, as a dev tool. Productize it downward: acceptance-criteria checks → blind second-provider judge → trend in.spec-context.json. Keep it optional, local, on-demand (Langfuse ~$300/mo always-on; Evalite free).
| # | Title | Why it lands |
|---|---|---|
| 1 | "Is Spec-Driven Development Already Obsolete?" | Rides the hottest debate; steelman the critiques, land on evals. |
| 2 | "Brownfield SDD: Adopt Specs in an Existing Codebase" | The most-requested capability; barely covered well. |
| 3 | "Stop Trusting 'Done': Verified Completion w/ a Second-Model Review" | Finger-guns + cross-provider review, live. |
| 4 | "Which Model for Which Step?" | Rides the Sonnet-5-vs-Opus war; routing across a pipeline. |
| 5 | "Spec Drift Is Killing Your Codebase" | Keep spec, code, tests in sync (Breunig's triangle). |
| 6 | "One GUI, Every Provider" | Companion demo framed against the "support my tool" flood. |
| # | Opportunity | Roadmap tie |
|---|---|---|
| 1 | Cross-provider as the headline + widen the provider matrix — the #1 demand; the wedge. | positioning + core |
| 2 | Adversarial cross-model plan review — uniquely enabled by cross-provider. | Wave 3 · W3·2 |
| 3 | Clarify-first interrogation gate — the most-validated pattern. | Wave 3 · W3·4 |
| 4 | Verified completion, not self-reported — closes the finger-guns gap. | verifier → mark-complete |
| 5 | Optional per-spec eval layer — reuses the bench judge + cross-provider. | new |
| 6 | Brownfield adopt + spec-editing / drift — the most-requested capability. | Wave 4 |
| 7 | Reposition the trace as context-durability + anti-lock-in. | core trace |
| 8 | Agent teams / "compare implementations" worktree view. | Wave 5 fan-out |
| 9 | Model/effort routing + token-budget pause; gray-box plans. | classify + auto-mode |
| 10 | HTML plan view; glossary; negative-constraints; spec-derived tests; post-implement refactor node. | assorted |
- Wave 3 priorities are right — interrogation and adversarial verification are the two most common patterns.
- Lean-by-default was correct — the credible voices warn against ceremony; "present but latent" is where the field is converging.
- Cross-provider is underused as a story — framed as flexibility, it's actually the #1 unmet need and the substrate for the highest-leverage features. The most valuable reframing here.
- The honest gap — brownfield/living specs + verified completion are where the field moves fastest and Companion has the most ground to cover. Already named in the roadmap — treat as near-term.
GitHub issues — mined by reactions + freshest-open (Issues only; Discussions not yet searched)
github/spec-kit — #1191 edit existing specs · #442 post-impl debugging · #377 multi-agent · #9 Cursor · #58 Warp · #1213 Antigravity · #30 Codex · #1414 model resolution · #3272 preset not installed
Fission-AI/OpenSpec — #662 hierarchical specs · #821 /opsx:repair · #689 standard skills folder · #1104 .agents installer · #202 Zed · #780 Superpowers skill pack · #869 Opus 4.6 skips the step
obra/superpowers — #429 Agent Teams · #895 plans over-specify · #743 slowness · #1878 Sonnet 5 fights the instructions · #270 Antigravity · #128 Gemini CLI · #1859 Hermes harness
bmad-code-org/BMAD-METHOD — #285 OpenCode · #320 Augment · #383 Warp · #301 Zed · #1613 agent teams · #2538 AI slop in code · #2512 post-impl refactor workflow
Medium articles — full per-article debrief on its own page
The 10 you flagged plus ~25 discovered, grouped by camp with expandable digests: → The Medium Articles, Debriefed.
Key voices: Kapil Ahuja (SDD-collapse → IDSD/ICE), Jarek Wasowski (facts / BDD / 15-framework map), Enrico Papalini (SDD-as-infrastructure / governance), Rick Hightower (framework layers), and Falk Gottlob (the "kill both" rebuttal).
Videos — 44, with 16 deep notes
Full per-video map: the playlist index · deep dive: the video trends report.
The near-term move
Lead with the one-two punch only Companion can ship cleanly: a clarify gate up front, and a second-model review before "done" — both riding the cross-provider strength that the whole category is begging for. Then close the brownfield + verified-completion gap where the field is moving fastest.
Component reports: Video Trends · Medium Debrief · refreshed weekly by the demand-radar skill.
Sourcing: GitHub & YouTube signals are firsthand. Most Medium bodies are member-paywalled — those digests lean on previews + titles + author list pages; deep claims behind the wall are flagged as unread. Nothing invented.