Determine when to use plan mode vs direct execution
What you should be able to do
- Select plan mode for large-scale, multi-file or architecturally significant work.
- Select direct execution for a well-scoped change with a clear cause.
- Use the Explore subagent to keep verbose discovery out of the main context.
- Combine the two — plan the approach, then execute it directly.
Exam traps (4)
Use plan mode for everything, since planning before acting is good practice.
A one-line fix with a clear stack trace gains nothing from a planning round and pays latency and tokens for it every time.
Plan mode earns its cost when there are several valid approaches or the change is wide.
Go straight to execution on a migration because the target is already decided.
Deciding the destination is not the same as knowing what it touches; the rework surfaces after the edits are spread across dozens of files.
Breadth is the trigger for planning, independent of how settled the goal feels.
Run the discovery phase in the main conversation so the findings are on hand.
Discovery is the most verbose phase, so it exhausts the window before implementation begins and the summary competes with raw output.
Isolate discovery in the Explore subagent and bring back the summary.
Treat plan mode and direct execution as a single choice for the whole task.
It forces planning overhead onto mechanical steps, or skips planning for the one decision that needed it.
Plan the investigation, then execute the agreed approach directly.
Primary sources
- Claude Code — common workflowschecked 2026-08-15
- Claude Code — interactive modechecked 2026-08-15
Know cold
- Planning mode
- Explore subagent
- Context window
6 practice questions in the bank are tagged to this task statement.
Practise this task in context: open it inside the interactive study guide, which carries the concept cards, the mock quiz and the practice simulation.