Spec-Driven Development: Sharpening your AI toolbox

AI coding tools are powerful—but without a solid spec process, delivery can become hard to reproduce and hard to trust. This talk walks through spec-driven development in Kiro and shows how structured artifacts can bring more control and reliability into an AI-assisted workflow. Key takeaways Covers how Kiro turns a prompt into requirements (with acceptance criteria), design, and a task list you can execute. Breaks down the EARS format (Easy Approach to Requirements Syntax) and why structured natural language matters for later automation. Explains how requirements can be translated into correctness properties for property-based testing, tying specs to code behavior. Shows how to use MCP servers across requirements, design, and implementation—and how to customize artifacts (e.g., wireframes, explicit test cases).