Warsaw AI Summit

Transcript

1. Spec Driven Development Vibe Coding Done Right Daniel Sogl daniel.sogl@thinktecture.com Principal Consultant | Speaker
2. Daniel Sogl About me Spec Driven Development Vibe Coding Done Right Principal Consultant @ Thinktecture AG Focus Developer Productivity & Gen AI MVP Developer & Web Technologies Socials linktr.ee/daniel_sogl
3. AI Agents Fail More Than You Think Spec Driven Development Vibe Coding Done Right The Problem Sources: SWE-Bench Pro (Sep 2025), Stack Overflow Survey 2025, CodeRabbit Report (Dec 2025) <25% 66% 2.74x
4. Spec Driven Development Vibe Coding Done Right Five Core Limitations Of AI Coding Agents Context Management "Lost in the middle" despite 200K+ token windows Multi-File Coordination No real-time dependency graphs, missed instructions Silent Failures Removes safety checks, generates fake data silently Architecture Decisions Sees structure but doesn't understand trade-offs Enterprise Context Missing implicit business logic and unwritten rules
5. Four Mechanisms How Specs Improve AI Spec Driven Development Vibe Coding Done Right Spec Driven Development Treat AI agents like literal-minded pair programmers, not search engines Complete Context Agent gets full picture upfront 1 Structured Reasoning Reduces hallucinations 2 Validation Checkpoints Humans verify before proceeding 3 Autonomous Implementation Specs + tests = guardrails 4
6. Spec Driven Development Vibe Coding Done Right How SDD Relates to TDD and BDD SDD What & Why Intent Level Human writes intent BDD System Behavior Feature Level Given / When / Then TDD Code Correctness Unit Level Red / Green / Refactor
7. Aspect OpenSpec Spec Kit Language TypeScript Python & Shell Commands 5 (lightweight) 8 (comprehensive) Workflow proposal → apply → archive specify → plan → task → implement GitHub Stars 21k 66k Best For Brownfield (1 → n) Greenfield (0 → 1) Spec Driven Development Vibe Coding Done Right OpenSpec vs. GitHub Spec Kit Hybrid Approach: Use Spec Kit for greenfield, then switch to OpenSpec for maintenance
8. Real Results Spec Driven Development Vibe Coding Done Right Practical Implementation 250k Developers in 3 Months AWS Kiro - The New Stack 94% Satisfaction Score Delta Airlines (re:Invent) 16k+ Spec Kit Stars in Week 1 GitHub (Sept 2025) Specs are the new code. 80-90% of our work as programmers is structured communication Sean Grove, OpenAI Sources: AWS Kiro, AWS re:invent (2025), The New Code – AI Engineer (2025)
9. Walking Through the 4 Phases Spec Driven Development Vibe Coding Done Right SDD In Action Specify Plan Task Implement YOU AI + YOU AI AI
10. Boundaries Before Code Spec Driven Development Vibe Coding Done Right Constitution
11. The only file you write by hand Spec Driven Development Vibe Coding Done Right The Spec
12. From intent to architecture Spec Driven Development Vibe Coding Done Right The Plan
13. Atomic, parallel, ready to execute Spec Driven Development Vibe Coding Done Right The Tasks
14. All green. Spec validated. Spec Driven Development Vibe Coding Done Right Implementation
15. Spec Driven Development Vibe Coding Done Right Where SDD Excels Greenfield Projects Spec becomes single source of truth Complex Features Agents need structure to avoid breaking contracts Multi-Agent Coordination Specs prevent conflicting implementations Compliance & Audit Specs as traceable control surfaces Rule of thumb: If it takes 2+ prompts to explain, write a spec.
16. Know the Limits Spec Driven Development Vibe Coding Done Right When NOT to Use SDD Small Bug Fixes Spec overhead exceeds the change Rapid Prototyping Uncertain requirements — specs need clarity UI-Heavy / Creative Work Visual design needs iteration, not specs One-Off Scripts Throwaway code — just vibe code it Rule of thumb: If you can explain the task in one sentence, skip the spec.
17. Vibe Coding Done Right Spec Driven Development Exceptional at pattern completion, not at mind reading.
18. Thanks for your attention Daniel Sogl @sogldaniel https://linktr.ee/daniel_sogl