Plan Mode: Get the Plan Before the Work

In short

In Plan mode Claude looks, explores, and tells you what it would do — without touching anything.
It's there to catch early that you'd each understood something different.
Your role changes: from executor to approver.
Not for everything: it pays off on large jobs or where the path isn't obvious.

"Tell me what you'd do first"

With a new collaborator, before an important job, you wouldn't say "go ahead." You'd say: "walk me through how you're planning to do this." Not because you don't trust them — because in two minutes you find out whether you're both picturing the same thing.

Plan mode is that gesture. Claude goes and looks at the situation — opens the files, builds a picture, explores — and then shows you a plan instead of executing it. Your files, meanwhile, stay untouched.

It's the first rung on the ladder of modes: the most cautious of all, and — paradoxically — the one that makes you work better, not just safer.

What's actually happening while it plans

Careful not to mistake it for a pause. In Plan mode Claude is genuinely working: it reads your files, looks at how the folder is organized, builds a picture. It just stops before writing anything.

And that's exactly what makes the plan useful: it isn't an invented outline, it's an outline built by looking at the real situation.

The cheapest moment to catch a misunderstanding

This is the real payoff, and it isn't safety. When you read the plan, almost always one of three things happens:

It all checks out. You give the go-ahead and move on with confidence.
Something's missing. You catch it while reading, tell Claude, the plan updates. Cost: one sentence.
It had understood something different. This is the golden case. Because that misunderstanding existed either way — the only difference is whether you find out now or after the work is done.

Fixing a line of the plan costs a sentence. Catching it afterward costs the finished work, plus the work of undoing it.

Your role changes

There's a side effect worth being aware of: with a plan in front of you, you stop being the one who executes and become the one who approves.

It's a different skill, and it has to be learned: reading a plan carefully, asking what's missing, saying "no, do it this way instead." The people who get the most out of these tools aren't the ones who write the most elaborate requests: they're the ones who read plans well.

When to use it, and when it's overkill

Yes when the job touches a lot of things at once, when the path isn't obvious, when undoing it would be a mess.
No when the task is tiny: if the plan is longer than the work, the plan is overkill.

In the desktop app you pick it from the modes next to the text box. From the terminal you get there with the shortcut that cycles through modes. And if you don't feel like looking for it, the poor man's version also works: just tell it — "don't change anything, first tell me how you'd do it" — which gets you nearly the same result with one thing missing: the guarantee. The real plan is the one where the files can't be touched, by construction.

What's next

The plan tells you what Claude intends to do. The other half of the problem remains: once it's done, how do you know if it turned out well? In the next lesson you'll learn to give it a yardstick.

Did you get it?

Two minutes, no grade. Trying to answer — even getting it wrong — cements the concepts far more than rereading. Not in the mood? Skip it: the lesson still counts as complete.

What can Claude do in Plan mode?

What's the real payoff of planning first?

Which jobs is it worth switching to plan mode for?

1
1. 1
2. 2
3. 3
2
1. 4
2. 5
3. 6
4. 7
3
1. 8
2. 9
3. 10
4. 11
5. 12
4
1. 13
2. 14
3. 15
4. 16
5. 17
6. 18
5
1. 19
2. 20
3. 21
4. 22
5. 23
6. 24
6
1. 25
2. 26
3. 27
4. 28
5. 29
6. 30
7
1. 31
2. 32
3. 33
4. 34
8
1. 35
2. 36
3. 37
4. 38
9
1. 39
2. 40
3. 41
10
1. 42
2. 43
3. 44
11
1. 45
2. 46