Plan mode
Plan mode is an operating mode in which an agent analyzes a task and outlines intended actions or plans without carrying out implementation changes.
Spec-Driven Development
Plan mode is an agent interaction pattern in which an AI agent presents its intended implementation approach before modifying code.
- How it is used
- Inserts a reviewable approach between a prompt and code changes to expose the agent’s interpretation before implementation.
- 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 you can do after
- Evaluate and revise an agent’s proposed approach before authorizing implementation.
Vibe Engineering
Plan mode is an AI-assistance mode that outlines intended development steps before modifying code.
- How it is used
- Separates AI-assisted planning from code execution so developers can review intended changes before accepting them.
- How deep it goes
- Describes planning, approval, diff review, and incremental commits, but stops short of specifying planning algorithms or agent internals.
- Examples
- Uses payment retry planning, migration-step mapping, unified diffs, and Git commits as concrete applications.
- What you can do after
- Apply it via Cursor or similar AI coding tools to review planned changes before execution and organize migration increments.
Claude at Work
Plan mode is an operating mode in which an AI coding agent produces planning documentation instead of implementation code.
- How it is used
- Uses planning sessions to align on decisions before Claude Code implements work that needs frequent feedback.
- How deep it goes
- Iterates from overall strategy to delivery and implementation plans, stopping short of code until execution is approved.
- Examples
- Plans an overall strategy, staged deliveries, and feature implementations; uses Gherkin generation as a review checkpoint.
- What you can do after
- Apply it in Claude Code to review plans and control when implementation begins.
What to know first
- CursorCursor is an AI-powered code editor that integrates artificial-intelligence assistance into software development.
Related concepts
- vibe codingcontrasts with · Vibe coding is a software-development approach in which natural-language direction guides an AI system to generate code, typically through iterative interaction.
- Claude Codeimplemented by · Claude Code is Anthropic’s command-line AI coding agent for inspecting and modifying codebases and carrying out software-development tasks through natural-language interaction and tools.
- delivery planproduces · A delivery plan is a staged plan that organizes work into manageable increments for producing and reviewing a deliverable.
Questions about plan mode
What is plan mode?
Plan mode is an operating mode in which an agent analyzes a task and outlines intended actions or plans without carrying out implementation changes.
Which Manning books explain plan mode?
Spec-Driven Development, Vibe Engineering and Claude at Work.
What should I know before learning plan mode?
Manning books that teach plan mode usually introduce Cursor first.
What is the difference between plan mode and act mode?
Plan mode is an operating mode in which an agent analyzes a task and outlines intended actions or plans without carrying out implementation changes. Act mode is an operating mode in which an agent is permitted to modify files or otherwise perform task actions.
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.


