Get Started
Build with Claude Code

Mission 3 of 7

Plan mode and the two-message rule: plan first, then build in small steps.

Ask for a big feature in one message and it starts typing in three seconds. Plan first, split the plan into steps, and you can review each piece before it becomes code.

55 minIntermediateFree (uses your existing Claude Code setup)Step 1 free

What you'll do

Plan in a read-only mode

Enter plan mode, where Claude Code can explore and propose but cannot write a file until you say so.

Review the plan, then split it

Catch the one expensive decision, then turn the plan into numbered steps that each have a test.

Build one step at a time

Run the loop of one step, one diff, one test and one commit, and know how to recover when a step goes wrong.

  • Review a plan in five minutes like a tech lead
  • Resume from a saved plan file if a session dies
Before you start
  • Claude Code with a decent CLAUDE.md in place
  • A real feature you've been putting off. Medium-sized: a few files, a data change, some UI
  • Git, with a clean working tree. You'll be committing after each step
Your progress0/6
01/06Why the first draft of a big feature is always wrong0 done
STEP 01 of 06~5 min

Why the first draft of a big feature is always wrong

Understand what goes wrong when it starts coding immediately, so the fix makes sense.

The two-message rule only sticks if you can see why it's needed. So start with what actually goes wrong when you hand over a big feature in one go.

Twenty silent decisions

When you give it a big feature in one message, it has to make twenty decisions before it writes the first line: where the data lives, what the API looks like, how existing records migrate, what the UI needs.

It makes all twenty silently, in a fraction of a second, and then builds on them. If decision three was wrong, decisions four through twenty are built on sand, and by the time you see the result there's no clean place to intervene.

How a senior engineer works

A senior engineer doesn't work like that and neither should the tool. They'd sketch the approach, show it to someone, get the data model challenged, then build in small pieces.

Each piece is reviewable. A mistake at step three is caught at step three.

Plan mode gives you the sketch. The two-message rule gives you the small pieces. Together they turn a coin-flip into a process.

Tip
The rule of thumb for 'big': if you can't picture the whole diff in your head, plan first. Bug fixes, renames and one-file changes skip it. Anything touching a database, more than three files, or a public API doesn't.
Checkpoint
You can explain, in one sentence, why a single big request produces worse code than ten small ones. Now you'll put the first half of the fix into practice.
Stuck? Ask the community
Next mission · Build with Claude CodeGive Claude Code hands: a browser, your database and GitHub through MCP
→