Skip to content

Browse catalog

Search catalog

[READY] Type a title, tag, or description.

NOTES // rule

Plan mode decision tree

LAST_MODIFIED
2026.10.07
CATEGORY
rule

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 modeSkip it
Approach is uncertainFixing a typo or adding a log line
Change spans multiple filesRenaming a single variable
Unfamiliar codebaseScope 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. For a hard guarantee, add the PreToolUse hook or climb the sandbox ladder. After implement, still verify before done.

Full playbook: Claude Code plan mode.

Sources

  1. Best practices for Claude CodeAnthropic
  2. Choose a permission modeAnthropic
claude-codeplan-modeworkflow

Related_Notes