Using Spec-Driven Development for Production Workflows
summary
Claim: spec-driven development splits complex features into three phases — requirements, design, implementation — and uses AI coding assistants to steer work. Evidence: Kiro IDE and CLI generates EARS-formatted requirements, mermaid designs and a task list; property-based tests with fast-check validate requirements; MCP protocol pulls Jira/Asana data. Surprise: an MVP appears by taking the top four tasks and delivers a browsable movie grid with search, filtering and sorting, which the demo implements and tests end-to-end.
AI-written summary · about
chapters (10)
- 0:00Spec-driven development intro
- 1:05Adopting spec-driven workflows
- 3:54Key considerations
- 6:40AWS Qiro tool
- 8:50Manual spec-driven dev
- 10:36Specs for legacy projects
- 11:40Requirements and design docs
- 13:04MCP integration
- 14:48Live demo in Kiro
- 17:15Summary and resources
related talks
28mHow To Use Spec-Driven Development for Production Workflows
47mSpec-Driven Development with AI Agents From High-Level Requirements to Working SW
01h 04mSpec-Driven Development: Agentic Coding at FAANG Scale and Quality
37mSpec Driven Development: AI Assisted Coding With Doc at the Core
25mFrom Vibe Coding to Spec-Driven Development
44mSpec-driven Development: How AI Changed Everything (And Nothing)
38mGet Shit Done with Get Shit Done - Spec-Driven development in AI times
45mSpec-Driven Development in the Age of Agents