liveBook · Manning

Chapter 1: Introduction to Intent-Driven Development

What you will learn in chapter 1 of Spec-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.

After this chapter you will be able to

Section by section

Introduction

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

Key terms: coding agents, intent articulation, intended outcomes, Intent-Driven Development, implicit human intent, effective context

1.1 Understanding intent

This section explains why IDD preserves articulated intent in durable artifacts that can outlast any one implementation.

Key terms: IDD, shared intent, durable artifacts, specifications, tests, source of truth, intent, translation loss, original prompt, implementation

1.1.1 Stating requirements without making intent explicit

Shows how a coding agent can satisfy stated requirements yet miss the intended outcome when important context remains unstated, and argues for making that intent explicit.

Key terms: requirements, underlying intent, interpretation gap, session invalidation, implicit-knowledge holder, coding agent, model capability, model training, intent articulation

1.1.2 What is “Intent”?

Defines intent as an actionable expression of purpose and shows how making that purpose explicit guides decisions about a feature.

Key terms: intent, purpose, intent articulation, downstream decision, verification criteria, active sessions, intent surfacing

1.1.3 What "Intent" is not?

This section distinguishes intent from vague feelings, possible ideas, and broad objectives, and places intent within the wider context needed to achieve an outcome.

Key terms: intent, intuition, ideas, objective, context, intended outcome

1.1.4 Intent articulation for AI

This section explains why AI coding needs explicit, conversational intent articulation, and why even agent interviews need a focused starting point.

Key terms: intent articulation, intent, requirements document, shared understanding, vibe coding, assumptions, outcome alignment, plan mode, initial prompt, interview

1.2 Intent articulation before AI coding

The section shows how user stories, BDD, and TDD made intent explicit before AI coding, and how Spec-Driven Development builds on that practice.

Key terms: user stories, so that, acceptance criteria, intent, Behavior-Driven Development, BDD, Gherkin, shared understanding, shared artifacts, Test-Driven Development

1.3 How intent-driven development works

The section explains how intent-driven development turns structured dialogue into durable intent and organized context so an agent can execute independently despite context-window limits.

Key terms: context window, compaction, durable artifacts, intent articulation, structured dialogue, discovery, durable intent artifacts, verifiable intent, context engineering, hierarchy of information

1.4 Harnessing intent

This section explains how an intent harness turns ideas into durable artifacts that guide an execution harness to produce aligned software.

Key terms: agent, model, harness, execution harness, intent harness, structured dialogue, intent artifacts, context, durable intent artifacts, specifications

1.4.1 Intent articulation mechanisms

This section explains how an intent harness uses specifications or autonomous iteration loops to connect articulated intent with execution, and when each approach fits.

Key terms: Spec-Driven Development, What (Discover), How (Design), Tasks, durable intent artifacts, autonomous iteration workflows, governing constraint, Ralph Loop, learning input, intent harness

1.5 Intent articulation is the new bottleneck

The section explains why poorly articulated intent becomes a bottleneck when coding agents increase the pace of implementation.

Key terms: intent articulation, human-centric workflows, misaligned outcomes, coding agents

1.5.1 No mental model of the code

The section explains why agent-generated code can leave engineers without a mental model of their application, turning review into a bottleneck despite faster code generation.

Key terms: mental model of the application, coding agents, mental model, review, intent-articulation problem

1.5.2 Fix intent articulation, not the implementation

The section argues that when an agent builds the wrong thing because intent was incomplete, teams should clarify the intent and regenerate the implementation rather than rely on more review or patch the faulty code.

Key terms: review agent, original intent, session invalidation, incomplete intent articulation, specification, acceptance tests, regenerate, revised intent, context burden, source of truth

1.6 When not to use Intent-Driven Development

This section explains when a quick vibe-coding approach may be preferable to IDD and why effective IDD adoption requires organizational collaboration.

Key terms: Intent-Driven Development, IDD, Vibe Coding, stakeholders, organizational capability, cultural alignment, Specfall, shared control surfaces

1.7 What do you need for the rest of this book

This section explains the tools and experience needed to complete the book’s exercises, while emphasizing that no particular coding agent or prior SDD practice is required.

Key terms: agentic coding tool, Git, GitHub, CLI, text editor, SDD, coding agent, containerized options

1.8 Summary

The chapter summary connects actionable intent, durable human–AI articulation, and intent-guided agent execution to the bottleneck created by faster code generation.

Where this is used later

Concepts explained in this chapter

Chapter 2: Writing Your First Specification →

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.