From Vibe Chaos to the Rise of Spec-Driven
summary
Looks at moving from ad-hoc “vibe” prompt-and-fix AI coding to Spec-Driven Development by using living specifications, execution plans and testable tasks. Covers concrete practices for writing specifications the AI must follow, a workflow to produce reliable code without endless prompt iteration, and a method to turn chaotic repos into a scalable process using AI as a tool rather than a source of repeated fixes.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:23Speaker introduction
- 2:29From B-coding to B-chaos
- 4:16Spec Driven Development
- 5:42Specit tool and install
- 7:05Project constitution definition
- 10:15Technical constitution details
- 13:49Product spec and PRD
- 15:36Requirements clarification
- 18:04Technical implementation plan
- 21:13Task breakdown
- 25:29Agent-guided implementation
- 33:21Spec Driven benefits
- 36:57Context engineering and hallucinations
- 38:00agents.md file and principles
- 40:52Using skills for precision
- 43:17Summary and Solo Leveling analogy
- 45:25Conclusion
- 46:08Q&A
related talks
45mSpec-Driven Development: the New Era of Development
25mDemystifying Spec Driven Development
25mFrom Vibe Coding to Spec-Driven Development
39mFrom vibe coding to spec-driven development
28mHow To Use Spec-Driven Development for Production Workflows
37mSpec Driven Development: AI Assisted Coding With Doc at the Core
47mSpec-Driven Development with AI Agents From High-Level Requirements to Working SW
44mSpec-driven Development: How AI Changed Everything (And Nothing)
