# Plan mode decision tree

> Use plan mode when the approach is uncertain, the change spans files, or the code is unfamiliar. Skip it for one-line diffs - typos, renames, log lines.

URL: https://bartlomiejkrupa.dev/notes/plan-mode-decision-tree/
Category: rule | Updated: 2026-10-07
Summary: Use plan mode when the approach is uncertain, the change spans files, or the code is unfamiliar. Skip it for one-line diffs - typos, renames, log lines.

**Plan mode** separates exploration from execution: Claude reads and drafts a plan but makes no edits until you approve. Enable with `Shift+Tab` mid-session or `claude --permission-mode plan` at startup. Edit the plan with `Ctrl+G` before proceeding.

## Rule

| Use plan mode | Skip it |
| --- | --- |
| Approach is uncertain | Fixing a typo or adding a log line |
| Change spans multiple files | Renaming a single variable |
| Unfamiliar codebase | Scope and fix are already clear |

Anthropic's loop: **explore → plan → implement → commit**. If you can describe the diff in one sentence, skip the plan - the overhead is not worth it.

## What the harness actually enforces

The plan is a markdown file in `~/.claude/plans` by default. Plan mode blocks Claude's edit tools until you approve, but shell commands still run while planning and sessions with bypass permissions available skip the block - see the [read-only hook](/notes/pre-tool-use-read-only-hook). For a hard guarantee, add the PreToolUse hook or climb the [sandbox ladder](/notes/sandbox-ladder). After implement, still [verify before done](/notes/verify-before-done).

Full playbook: [Claude Code plan mode](/articles/claude-code-plan-mode).

Sources:
- Best practices for Claude Code: https://code.claude.com/docs/en/best-practices
- Choose a permission mode: https://code.claude.com/docs/en/permission-modes
