liveBook · Manning

Plan mode

As explained in Spec-Driven Development

Plan mode is an agent interaction pattern in which an AI agent presents its intended implementation approach before modifying code.

Plan mode inserts a reviewable approach between a prompt and implementation. It makes the agent’s interpretation and understanding of the existing code visible before changes begin, reducing reliance on assumptions that would otherwise surface only after execution. section 1.1.4 section 2.3.2

Use the plan as an early alignment checkpoint:

  • Ask for a plan describing the intended changes and their order. section 2.3.2
  • Review the plan and request revisions until it reflects the intended change; then allow implementation to proceed. section 2.3.2
  • Treat the plan as a useful check, not a guarantee: its quality remains probabilistic and depends on the initial prompt. section 1.1.4

Password reset

A request to build a password reset feature without stating its purpose may lead the agent to ask about email providers, password rules, and rate limits, while missing the goal of securing a compromised account. Stating only the goal of preventing further misuse may instead broaden the discussion to alternatives such as two-factor authentication or an account freeze. Plan mode makes an interpretation reviewable, but an initial intent still helps orient the interaction. section 1.1.4

Figure 2.8 Plan mode makes the agent’s interpretation of our instruction explicit, reducing our dependence on the vibe.

The diagram places the reviewed plan between the prompt and implementation. section 2.3.2

How Spec-Driven Development covers it

How deep it goes
Details plan review, revision, and approval, while noting that plan quality remains probabilistic and prompt-dependent.
Examples
Uses a password-reset request to show how stating purpose changes the agent’s questions and proposed directions.
What it assumes
Assumes an initial prompt; explains that interviewing can surface omitted considerations but still needs articulated intent to guide questions.
What you can do after
Evaluate and revise an agent’s proposed approach before authorizing implementation.
How it connects
Connects prompting and requirements articulation to implementation, and contrasts plan mode with direct build mode.

Also explained in

Compare how 3 books explain plan mode →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Spec-Driven Development. The section links point to the parts of the book it draws on.