Plan before you act

Last lesson you learned to spot a big task. This is what to do the moment you do. Claude has a mode built for exactly this — and most people go months without finding it.

Plan mode is a setting where Claude reads, explores, and proposes a plan — but doesn’t change a single file until you say go.

You turn it on by pressing Shift+Tab to cycle through Claude’s modes until the status line says plan mode. Press it again to cycle back out. That’s the whole control.

What you get back

You ask your big question in plan mode, and instead of charging in, Claude hands you a plan: the steps it intends to take, the files it expects to touch, the decisions it’s making along the way. Nothing has happened yet. The plan is just words on your screen.

Then it waits. You read it. You approve it, or you push back, or you change your mind entirely — all before anything in your project has moved an inch.

If you did Level 6, this will feel familiar: plan mode is the most cautious member of the permission family. Where “allow once” lets an action through one at a time, plan mode holds all of them back until you’ve seen the whole shape of the work.

Why this is the cheapest insurance you’ll buy

Here’s the asymmetry that makes plan mode worth it:

• Writing a plan costs minutes. Reading one costs you thirty seconds.
• Un-doing a botched task costs hours. Reverting a 200-line refactor that went sideways, re-checking every file it touched, re-explaining what you actually wanted — that’s your whole afternoon.

It is always cheaper to disagree with a plan than to undo the work. Plan mode moves the disagreement to the cheapest possible moment: before any work exists.

This is the same instinct as measuring before you cut, or reading the recipe before you turn on the stove. The five minutes up front are not the slow part. The slow part is the do-over.

When to skip it

Plan mode earns its keep in proportion to the size of the task. For a typo fix or a one-line rename, it’s pure friction — you’d spend longer reading the plan than the change deserves. Don’t ceremony-up the small stuff.

The rule of thumb: the signals from the last lesson are also your plan-mode signals. Multiple files, real decisions, unknowns, fuzzy finish line — that’s when you reach for Shift+Tab. One clear small thing — just ask.

What’s next

Plan mode gets you a plan. But a plan is only useful if you actually read it — and most people rubber-stamp. The next lesson is how to read a plan like you mean it, and catch the problems while they’re still free.