What you will learn in Spec-Driven Development
Engineering with intent
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.
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.
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.
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.
What you learn in chapter 4 →Concepts explained in this book
- specificationA structured description of software intent, requirements, implementation constraints, and expected outcomes.
- specification-driven developmentA software development approach in which specifications produced through human–AI dialogue guide implementation.
- contextInformation supplied to an AI coding agent to guide its understanding and work.
- vibe codingVibe coding is software development guided primarily by natural-language direction and an informal sense that the generated result matches the developer's intent.
- durable artifactA durable artifact that records articulated intent to guide implementation.
- intent articulationIntent articulation is the practice of making a feature's underlying purpose explicit and connecting it to the required approach.
- ai coding assistantAn AI-powered tool that interprets development instructions and performs coding tasks.
- context engineeringContext engineering is the deliberate organization of relevant information so that a participant or system can understand and act on it effectively.
- Intent-Driven DevelopmentAn AI-native software engineering approach that translates implicit human intent into consistent language and systems that agents can use to guide software development.
- control authorityControl authority is the property of a specification whereby changing it directs system behavior and implementation in the intended direction.
- acceptance criteriaA verifiable condition used to determine whether a requirement or feature has been satisfied.
- compactionThe process of replacing earlier interaction content with a shorter summary when an AI agent approaches its context limit.
- context windowA context window is the bounded amount of information an AI model can consider during one interaction.
- implementation gapA discrepancy between behavior specified for a system and the behavior or coverage of its implementation.
- deterministic checkDeterministic verification is verification based on repeatable checks that produce evidence of whether a specified outcome has been achieved.
- intentIntent is the actionable expression of purpose for a specific change, concrete enough to guide implementation and verification.
- change proposalA documented set of intended modifications to an existing software system, including their requirements and potential impacts.
- specification authoringSpecification authoring is the structured process of eliciting intent and expressing it as a detailed feature specification.
- course correctionAn adjustment to an agent's instructions or direction in response to an observed mistake, assumption, or undesired result.
- intent harnessA higher-level harness that helps humans and agents articulate intent and produce durable artifacts that guide execution.
- intent lossIntent loss is the failure to preserve a human's intended meaning, requirements, or constraints across the stages of software development.
- implementation constraintAn implementation constraint is a restriction or boundary that limits how a software solution may be designed or built.
- dumb zoneA state in which an AI coding agent's crowded or compressed conversational context undermines its ability to work usefully and stay aligned.
- authoritative specificationAn authoritative specification is a specification with high control authority and high fidelity that governs system changes while accurately representing the application.
- decorative specificationA decorative specification is a specification that neither governs system changes nor accurately represents the code.
- reconciled specificationA reconciled specification is a specification reconstructed from an existing application that accurately describes the system but does not govern its changes.
- regeneration testA regeneration test checks whether regenerating an implementation from the same specification reproduces the same behavior.
- spec-anchoredA spec-anchored workflow keeps the specification in the feature lifecycle and updates it alongside the evolving implementation.
- spec-as-sourceA spec-as-source workflow treats the specification as the primary editable artifact from which an agent generates or updates the implementation.
- spec-firstA spec-first workflow creates a specification before implementation to guide an initial build without necessarily keeping the specification central afterward.
- underspecified specificationAn underspecified specification is a specification that governs changes but omits enough intent or detail to constrain implementation reliably.
- execution harnessAn agent harness specialized for independently carrying out tasks and generating implementations or other work products.
- plan modePlan mode is an agent interaction pattern in which an AI agent presents its intended implementation approach before modifying code.
- specification formatA specification format is a defined structure and notation for recording requirements and decisions with sufficient precision for implementation.
- OpenSpecA specification-driven development tool that provides workflows and artifacts for proposing, applying, and archiving changes.
- false positiveA result incorrectly judged to satisfy a condition when it does not.
- structured conversationAn interaction structured to elicit missing information and capture software intent in a specification.
- context debtContext debt is the absence of durable context needed to safely understand, maintain, and evolve software produced through agent interaction.
- intent alignmentThe state in which humans and agents share an aligned understanding of the intended software outcome before implementation.
- task phaseThe specification phase in which engineering decomposes design work into executable tasks and defines completion evidence.
- alignment regressionThe loss of previously achieved behavioral alignment as an implementation evolves and new features are added.
- governance loopA recurring process for detecting intent loss, correcting specifications and implementations, and improving the development workflow.
- specification bypassA change made directly to code without first being represented in the governing specification.
- time-to-aligned implementationThe elapsed time from an idea to the first implementation that satisfies intended behavior, construction constraints, and verification evidence.
- product specialistA product-side participant who clarifies feature intent and defines what a feature should accomplish.
- specification-to-implementation alignmentSpecification-to-implementation alignment is the degree to which an implementation conforms to the behavior and constraints expressed in its specification.
- test-driven developmentTest-driven development is a software development practice in which an automated test is written before the implementation that makes it pass.
- autonomous actionAn AI agent's ability to complete an implementation task without continuous human intervention.
- specfallA dysfunctional adoption pattern in which specifications become documents to produce and circulate instead of shared control surfaces for intended software behavior.
- granularitySpecification granularity is the level of detail at which a specification describes required behavior and implementation constraints.
- requirements structureRequirements structure is the organization and formalization of requirements statements, including their grammar and behavioral expression.
- scope of authorshipScope of authorship is the set of participants, roles, and locations permitted to create or contribute to a specification.
- specification organizationThe arrangement of specifications across features, system state, or both.
- verifiability mechanismA verifiability mechanism is a process or technical facility for checking alignment between a specification and an implementation.
- intent elicitationIntent elicitation is the process of drawing out a person's intended purpose, requirements, and constraints through interaction.
- business contextThe set of purpose, scope, user, problem, and success information that explains why a feature or change is needed.
- technical approachThe planned way a feature or change fits into an existing architecture and is implemented under its technical constraints.
- behavior-driven developmentBehavior-driven development is a software development practice that specifies system behavior collaboratively using examples and shared language.
- user storyA user story is a concise requirement expressed from the perspective of a person who needs a capability and its purpose.
- autonomous iteration workflowAn autonomous iteration workflow is a repeated execution process steered by governing constraints toward learning and convergence.
- specification gapMissing or incomplete information in a specification that can cause an implementation to diverge from the intended behavior.
- governing constraintA governing constraint is a rule or boundary that directs repeated execution, learning, and convergence in an autonomous workflow.
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.
