Share
Embed
Spec Driven Development: The End of Vibe Coding
One small feature, start to finish: a dark/light mode switch, built once from a single sentence and once through GitHub Spec Kit. What Spec-Driven Development is, how the flow works step by step, what it buys you and where it still fails.
VibeKode Berlin, November 18, 2026.
Daniel Sogl
November 18, 2026
Transcript
36 slides
-
Spec Driven Development One small feature, start to finish. Daniel
Sogl Director of AI Engineering · SHI GmbH · Microsoft MVP VibeKode Berlin Nov 18, 2026 -
Daniel Sogl Director of AI Engineering · SHI GmbH ·
Microsoft MVP 50+ client workshops on AI-assisted development in four years Teaching teams to work with coding agents Building up AI engineering at SHI, with agents in real client projects [email protected] Spec Driven Development VibeKode Berlin · 2026 daniel-sogl danielsogl 2 / 36 -
64 seconds later A sun icon in the navbar. Lint,
unit tests and build pass. Spec Driven Development VibeKode Berlin · 2026 4 / 36 -
What I never said FROM THE AGENT'S FINAL MESSAGE, SHORTENED
"Once the user clicks the toggle, their choice … wins from then on." "… will see a brief flash of the system theme on load … say if you want it." "I did not add a Playwright E2E test for the toggle." Reload with "dark" stored, on a device set to light. Bundle delayed by 1.2 s so the moment stays visible. All reasonable, and I chose none of it. Spec Driven Development VibeKode Berlin · 2026 5 / 36 -
The agent wrote clean code for a brief that left
the decisions open. -
Decide before the code exists PROMPT-DRIVEN Prompt Code Review decisions
happen here you find out here SPEC-DRIVEN Prompt Spec Plan Tasks Code decisions happen here Spec Driven Development VibeKode Berlin · 2026 8 / 36 -
What goes into a spec Intent Constraints Acceptance criteria What
and why? Goal, user stories, motivation. What rules apply? Scope, boundaries, what not to build. When is it done? Testable conditions the agent checks itself against. A spec describes behaviour. Frameworks and file names come later, in the plan. Spec Driven Development VibeKode Berlin · 2026 9 / 36 -
Three levels of commitment AFTER THE MERGE … Spec-first Most
teams today. Spec-anchored More value, more upkeep. Spec-as-source Still experimental. THE SPEC IS THE CODE IS left behind edited directly updated with every change edited directly the only thing humans edit regenerated from the spec Taxonomy: Birgitta Böckeler, "Understanding Spec-Driven Development", martinfowler.com (Oct 2025) Spec Driven Development VibeKode Berlin · 2026 10 / 36 -
The tool today: GitHub Spec Kit Open source, by GitHub,
public since September 2025 Agent-agnostic: Copilot, Claude Code and others One CLI command sets it up in an existing repo Each step is a slash command in the agent v1.4 ~150k ★ Everything it writes is Markdown in Git github.com/github/spec-kit (v1.4.0) · stars as of Nov 15, 2026 Spec Driven Development VibeKode Berlin · 2026 12 / 36 -
Seven steps, two of them yours Specify Clarify Plan Tasks
Analyze Implement Converge you + AI you answer you + AI AI AI AI AI Four steps run before any code. Each one leaves a file in the repo. Spec Driven Development VibeKode Berlin · 2026 13 / 36 -
0 · Constitution: the house rules Once per project. Every
plan is checked against it. I · Clear Boundaries II · One Idiom per Concern III · The Compiler Reviews First Every domain is split into layers. Dependencies point one way. Use the framework's current features directly. No legacy patterns. Strict types and explicit public APIs. IV · One Path for State V · One Theme VI · Gates Are Not Bypassed State changes go through the store, nowhere else. A single token-based theme, in one named file. Tests, lint and build pass. No skipped hooks. The six principles of the demo app's constitution, paraphrased from their rationales. Spec Driven Development VibeKode Berlin · 2026 14 / 36 -
1 · Specify: describe the behaviour USER STORY 2 ·
SELECTED MODE IS REMEMBERED GIVEN the user has selected dark mode WHEN they reload the page THEN the application is shown in dark appearance FR-007 FR-012 ASSUMPTION MUST show the matching appearance from the first visible frame MUST meet WCAG 2.1 AA contrast requirements The switch has two states (light and dark). spec.md, first version, shortened · in total 3 stories, 14 requirements, 6 edge cases, from one sentence Spec Driven Development VibeKode Berlin · 2026 15 / 36 -
2 · Clarify: the agent asks QUESTION 1, SHORTENED ·
HANDS UP, PLEASE Once a user has picked light or dark, should they be able to go back to "follow my device setting"? A B C Two states. The device setting applies only until the first choice. Three states: light, dark, follow device. Two states, and the app always starts in light. The agent recommended A. I chose B. Spec Driven Development VibeKode Berlin · 2026 16 / 36 -
My answers changed the spec FR-001 · AFTER QUESTION 1
exactly three modes: light, dark and system ASSUMPTION · BEFORE The switch has two states (light and dark). FR-002 · AFTER QUESTION 2 a single button … each activation advances the mode: light, dark, system, light I overruled the recommendation on both questions. spec.md before and after clarify, shortened Spec Driven Development VibeKode Berlin · 2026 17 / 36 -
3 · Plan: how, with reasons DECISION 5 OF 8
· NO FLASH OF THE WRONG APPEARANCE DECISION CONSEQUENCE REJECTED A small inline script in the <head> sets the mode on <html> before the stylesheet is applied. The storage key and the three valid values exist twice. An end-to-end test guards the pair. provideAppInitializer : runs after the bundle is downloaded and parsed; flashes. Every plan is checked against the constitution before it continues. research.md, section R5, shortened Spec Driven Development VibeKode Berlin · 2026 18 / 36 -
4 · Tasks: small, ordered, checkable PHASE 3 · USER
STORY 1 (P1) T005 P US1 Create theme-mode-store.ts T006 P US1 Create theme-mode-toggle.ts T009 P US1 Create theme-mode-store.spec.ts : initial mode is system … T012 US1 Create tests/theme-mode.spec.ts in the existing Playwright project PHASE 6 · POLISH T023 Manual walkthrough with WCAG 2.1 AA contrast inspection tasks.md, 5 of 24 tasks, shortened · P can run in parallel · US1 belongs to user story 1 Spec Driven Development VibeKode Berlin · 2026 19 / 36 -
5 · Analyze: cross-check before code Constitution Spec Plan Tasks
Code · not written yet Rule against reality Requirement without a Flaky by design The constitution wants the theme in a file that doesn't exist in the app. check A unit test would read whatever the last run left in localStorage. "Switches within 200 ms" has no task that measures it. 11 findings, before a line of code. Spec Driven Development VibeKode Berlin · 2026 20 / 36 -
6 · Implement: work through the list 87 → 138
+18 unit tests end-to-end tests 23 / 24 tasks done cycle, keyboard, reload, no flash, 320 px One deviation, reported: the Material tooltip pushed the bundle to 540 kB, over the app’s 500 kB budget. The agent switched to a native tooltip and updated plan and tasks to match. Spec Driven Development VibeKode Berlin · 2026 21 / 36 -
7 · Converge: code against spec Spec Plan Tasks Code
Gap found Still open The native tooltip is drawn by the browser. The spec says tooltips must follow the active appearance. T023, the contrast inspection. "It needs a person, so implement cannot close it." New task: T025 24 of 25 tasks are done, and the open one is mine. Spec Driven Development VibeKode Berlin · 2026 22 / 36 -
The result System Light Dark One button with three modes
and no flash on reload: the switch I would have asked for. Spec Driven Development VibeKode Berlin · 2026 23 / 36 -
What the flow bought One sentence Through the flow Modes
light, dark light, dark, system · my call Reload brief flash of the wrong theme right from the first frame Tests one unit spec unit + 18 end-to-end Accessibility an aria-label keyboard, accessible name, contrast check pending Where the decisions live a chat message spec, plan and tasks in the repo Both versions are clean code. Only this one is the feature I meant. Spec Driven Development VibeKode Berlin · 2026 24 / 36 -
A lot of ceremony for a button One sentence Through
the flow Agent time Markdown to read Code and tests 1 min 19 min none 1,085 lines 189 lines 1,053 lines Somebody has to read all of that. Spec Driven Development VibeKode Berlin · 2026 26 / 36 -
It is only as good as what you feed it
Stale rules The plan moves Failing tests My constitution named a theme file that doesn't exist. The plan had to argue around it. The agent hit the bundle budget, changed course and rewrote plan and tasks itself. Three end-to-end tests were already failing. The agent noted them and moved on. The documents drift, so one review isn’t enough. Spec Driven Development VibeKode Berlin · 2026 27 / 36 -
What nobody has solved yet Review fatigue Specs go stale
Every step produces Markdown that someone should read. Skim it, and the agent is deciding alone again. The code keeps changing after the merge. Nothing fails when the spec no longer matches it. Teams Evidence Specs live in Git. Product, QA and domain experts can't co-author there, and nothing reconciles two specs that contradict each other. Nobody has shown yet that specs lead to fewer defects. The largest study so far found no effect. Spec Driven Development VibeKode Berlin · 2026 28 / 36 -
When is it worth it? Prompt it, or use plan
mode Spec it Bug fixes, prototypes, scripts Behaviour that users see Refactorings, even large ones Permissions, retention, anything you promise The open decisions are engineering: library, Product, QA or a domain expert has a say file layout, test structure Someone will ask later why it works this way You can judge the result from the diff Ask who owns the open decisions, whatever the size of the change. Spec Driven Development VibeKode Berlin · 2026 30 / 36 -
Three steps, cheapest first 1 Make it ask. One line
in your agent instructions: before building, list the decisions you are about to make for me, and ask about the ones that are not engineering. 2 Make the answers stay. Plans and decisions go into the repo, with the change. 3 Add the gates. Spec Kit, OpenSpec or Kiro, when the decisions are worth the reading. Spec Driven Development VibeKode Berlin · 2026 31 / 36 -
If you pick a tool GitHub Spec Kit v1.4 ·
~150k OpenSpec ★ v2.0 · ~75k Every step explicit. What you saw today. ★ Lighter, built for existing code: propose, apply, archive. Kiro IDE + CLI One turnkey environment with specs built in. github.com/github/spec-kit (v1.4.0) · github.com/Fission-AI/OpenSpec (v2.0.0) · kiro.dev · stars as of Nov 15, 2026 Spec Driven Development VibeKode Berlin · 2026 32 / 36 -
Three things to take home 1 A spec is where
you and the agent agree on done, before either of you writes code. 2 The value is in the questions. Answer them yourself. 3 It costs reading time. Spend it where the decisions are not engineering. Spec Driven Development VibeKode Berlin · 2026 33 / 36 -
Let’s build software that does what it says. Thank you!
Slides: linktr.ee/daniel_sogl Daniel Sogl Director of AI Engineering · SHI GmbH · Microsoft MVP [email protected] linkedin.com/in/daniel-sogl slides · contact -
Sources & further reading Studies SDD practice & tooling B.
Hill: "Specification Artifacts in Open-Source PR Workflows Do Not Reduce Defects", ESEM 2026, LIPIcs 394:84 Agarwal et al.: "SDD as Prescribed and as Practiced", arXiv:2608.25202 B. Böckeler: Understanding SDD, martinfowler.com (Oct 2025) M. Brooker: "Spec Driven Development isn’t Waterfall" (Apr 2026) github.com/github/spec-kit · github.com/Fission-AI/OpenSpec · kiro.dev Thoughtworks Technology Radar Vol. 35 (Nov 2026) Spec Driven Development VibeKode Berlin · 2026 36 / 36