liveBook · Manning

What you will learn in Spec-Driven Development

Engineering with intent

by Hari Krishnan · Manning Early Access Program (MEAP)

Chapter by chapter

Chapter 1: Introduction to Intent-Driven Development

The chapter introduces why coding agents make intent articulation more important and defines Intent-Driven Development as a way to guide their work.

1.1 Understanding intent · 1.1.1 Stating requirements without making intent explicit · 1.1.2 What is “Intent”? · 1.1.3 What "Intent" is not? · 1.1.4 Intent articulation for AI · 1.2 Intent articulation before AI coding · 1.3 How intent-driven development works · 1.4 Harnessing intent · 1.4.1 Intent articulation mechanisms · 1.5 Intent articulation is the new bottleneck · 1.5.1 No mental model of the code · 1.5.2 Fix intent articulation, not the implementation · 1.6 When not to use Intent-Driven Development · 1.7 What do you need for the rest of this book · 1.8 Summary

What you learn in chapter 1 →

Chapter 2: Writing Your First Specification

The chapter introduces SDD as aligning human and agent intent through specifications and argues for understanding its foundations before choosing tools.

2.1 What is a specification · 2.1.1 Tactical vs strategic context engineering · 2.1.2 Characteristics of a good specification · 2.2 How does SDD work · 2.2.1 Spec-driven development workflow · 2.2.2 Why the structure matters · 2.3 Need for spec-driven development · 2.3.1 Vibe coding software development lifecycle · 2.3.2 Context debt and the return to manual mode · 2.3.3 Unsuitable for sustained independent execution by agents · 2.3.4 Loss of predictability · 2.4 Spec-driven development by example · 2.4.1 Are you ready to specify? · 2.4.2 SDD Framework Setup · 2.4.3 Project Configuration · 2.4.4 Start specifying · 2.4.5 Implement the specification · 2.4.6 Specify the next feature · 2.5 What SDD Is Not · 2.5.1 Dispelling the Waterfall Comparison · 2.5.2 SDD adoption is not a developer tooling rollout · 2.5.3 SDD more than recovers specification time through parallel execution · 2.5.4 SDD is not just a markdown machine · 2.6 Summary

What you learn in chapter 2 →

Chapter 3: Keeping Specs Alive

The introduction explains why specifications must stay aligned with the system to keep guiding agent-generated work, and why implementation gaps should inform improvements to the SDD workflow.

3.1 Why specs go stale · 3.1.1 Misaligned implementation · 3.1.2 The direct fix trap · 3.1.3 The cost of repeated spec revision · 3.2 Feedback loops · 3.2.1 Intent Loss in Surfacing · 3.2.2 Intent Loss in Capture · 3.2.3 Intent Loss in Construction Constraint · 3.2.4 Intent Loss in Outcome Verification · 3.2.5 Fine-Tuning the SDD Workflow · 3.3 Specifying thoroughly without creating markdown mountains · 3.3.1 The specification is one part of the context · 3.3.2 Separating the repairs · 3.3.3 Invest where deviation is expensive · 3.4 Specification governance · 3.4.1 Defect leakage and attribution · 3.4.2 The governance operating loop · 3.5 How alive is a spec? · 3.5.1 Control Authority · 3.5.2 Specification fidelity · 3.5.3 The four states of specification · 3.6 Tooling landscape · 3.6.1 Taxonomy of spec styles · 3.6.2 Framework for evaluating tools · 3.7 Summary

What you learn in chapter 3 →

Chapter 4: Collaborating Across Product, Architecture, and Engineering

The chapter introduction explains why teams need shared specifications to onboard memoryless AI agent sessions and turn individual AI gains into team productivity.

4.1 Moving beyond solo SDD: collaboration patterns · 4.1.1 Three roles at the specification surface · 4.1.2 Engineer as scribe · 4.1.3 Passing the baton · 4.1.4 Mob authoring · 4.1.5 Asynchronous contribution through encoded expertise · 4.2 Specifying as a team · 4.2.1 Product specialist defines the what · 4.2.2 Architect shapes the how · 4.2.3 Engineer authors the tasks · 4.2.4 Beyond the three roles · 4.2.5 Standing context is grown, not installed · 4.3 Hands-on: building the URL shortener as a team · 4.3.1 Exercise Setup · 4.3.2 First slice: each role contributes its part · 4.3.3 Second feature: link expiration · 4.3.4 Reviewing the constitution · 4.4 Making the framework work for us · 4.5 Summary

What you learn in chapter 4 →

Concepts explained in this book

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.