Learn · Configuration & workflows · CCAR-F task 3.4
Plan mode vs direct execution
Plan mode lets Claude research but blocks edits until you approve. Use it for big or ambiguous changes; execute small, clear fixes directly.
Key ideas
- Plan mode (Shift+Tab or /plan) allows reading and research but blocks edits until you approve a plan.
- Use it for multi-file or architectural changes, several plausible approaches, unfamiliar code, or a costly wrong turn.
- Execute directly for a well-scoped bug with a clear cause, a rename or a typo.
- Claude often uses the built-in Explore and Plan subagents to research in a separate context.
- Strong pattern: plan, approve, execute, verify with tests.
Worked example: Monolith to microservices
Splitting a service out of a monolith touches many files and has competing designs, so start in plan mode, review the plan, then let Claude execute and run the tests. A one-line null check with a known cause doesn't need that ceremony.
Exam traps
- Executing a large architectural change directly, discovering the wrong design halfway through.
- Using plan mode for a trivial typo fix, adding delay for no benefit.
- Thinking plan mode lets Claude edit files before you approve the plan.
Official docs
Practise CCAR-F questions · Next lesson: Iterative refinement