Plan Mode: Make Claude Think Before It Edits
TL;DR
Claude tends to edit before it thinks, and you find the flaw after it has already changed things. Plan mode flips the order. Shift+Tab puts Claude in plan mode, where it maps the whole change first - so you catch the wrong step on paper, while it is still free to fix, and nothing runs until you approve the plan.
The default problem
Left alone, Claude jumps straight to doing - it edits, runs, and changes files, then you discover the flawed assumption three steps later, after it has already touched things. Unwinding that costs more than the original task. Plan mode removes the whole class of problem by making thinking the first step, not the last.
How to turn it on
Press Shift+Tab to cycle Claude's permission modes. One of them is plan mode. In plan mode, Claude reads and reasons about the whole change and writes out the plan - but it does not edit or run anything until you say go. Press Shift+Tab again to cycle back out when you are done.
The three things it changes
- It maps the whole change first - the full approach, in order - instead of improvising step by step.
- You catch the flawed step on paper, while it is still cheap to fix, instead of after files have changed.
- Nothing runs until you approve the plan, so you are never surprised by an edit you did not sign off on.
Read the plan like a reviewer
- 1Check the assumptions - does the plan believe something about the code that is not true?
- 2Check the order - will an early step break something a later step needs?
- 3Check the scope - is it doing more than you asked, or missing part of it?
- 4Only then approve. A flaw you catch here is free; the same flaw after edits is a debugging session.
Common questions
How do I enter plan mode?
Press Shift+Tab to cycle permission modes until you reach plan mode. Claude will then plan the change without editing or running anything until you approve. Press Shift+Tab again to cycle back out.
When should I use it versus just letting Claude go?
Use it for anything multi-step, risky, or in unfamiliar code - refactors, new features, changes near production. For a trivial one-line edit it is overkill. The rule of thumb: if a wrong approach would cost you real time to unwind, plan first.
Does plan mode cost extra?
It uses a little more thinking up front, but it routinely saves far more by preventing a wrong build you would have to debug and redo. Catching the flaw on paper is the cheapest place to catch it.
How is it different from permissions or guardrails?
Plan mode is about judgment - making Claude think through the approach before acting. Permissions are the hard limit on what it is allowed to do at all. They pair well: plan the right change, and let guardrails stop the dangerous ones regardless.
Want the plan-mode guide with the workflow?
Get 650+ plug-and-play skills, MCPs & prompts, plus 5,000+ builders - $9/mo, cancel anytime.
Join the Club