CCA-F start here · Trap gym · Plan or just do it?

Plan or just do it?

Claude Code can plan before it edits, or it can just make the change. The trap runs both ways. For a big change whose approach isn't settled, the wrong answers start editing straight away. For a one-line fix, they wrap it in plans, searches and questions. Learn to size the task first, and the right mode follows.

D3 Claude Code ConfigurationExam guide 3.4 and 3.5About 15 minutes

At a glance: Make a small, settled change directly; use plan mode for big, many-file or undecided changes, and send long searches to the Explore subagent.

Start here: hanging a picture, or redoing the kitchen

Think about two jobs at home.

Hang one picture. You know the wall, you have the nail. You just do it. Drawing a plan or calling a meeting first would only waste the afternoon.
Redo the kitchen. Walls, pipes, wiring, and two ways it could be laid out. You measure every room and agree the layout before anyone knocks down a wall. Knocking first means building some of it twice.

Claude Code works the same way. Direct execution is hanging the picture: Claude makes the change and runs the tests. Plan mode is the kitchen: Claude explores the code and proposes a plan, and nothing changes until you approve it. Three helpers fit around them:

Interview first if what's wanted is unclear The task size it first small, settled big or open Direct execution edit, then run the tests Tests first share the failures Plan mode explore, propose a plan, you approve, then edit Explore subagent does long searches, returns a summary search summary nothing changes until you approve
The one question to ask: is the approach already decided, and is the change small?

Words in the question that tell you which side you're on

Just do it

  • one, single, a check, a typo, a rename
  • “the file is known”, “the format already exists”
  • the ticket already states the rule
  • “quickest”, “most efficient”

Plan first

  • many files, folders, screens or services
  • migrate, restructure, replace, split
  • “two libraries”, “engineers disagree”, “not yet chosen”
  • “nobody has mapped…”, “how should they start?”

Try it: play out the task

Pick a task, then pick how you start it with Claude. The simulator plays out the steps, marks any rework in pink, and shows how much of the main session's context the work used. The diagram above highlights where your choice sits.

1. The task
2. How you start
explore or planquestions or approvaledittestsrework

    Main session context used:

    The minutes and context figures are illustrative, chosen to show the shape. They are not measurements. The exam guide's point is that plan mode prevents rework on big or open changes, and that a simple, well-scoped change needs no plan.

    Things to try: typo + plan mode, then typo + direct execution. Then library move + direct execution to watch the rework pile up, and library move + plan mode, then + Explore subagent to see the context meter drop. Last, CSV export + plan mode: a good plan built on a guess.

    The four traps

    TrapWhat the wrong option looks likeWhy it's wrong
    A plan for a small changePlan mode, an Explore subagent or an interview for a typo or one validation checkOverbuilt. The same edit, several times slower, and nothing in the plan was open.
    Just doing a big, open change“Convert one folder, then roll the pattern out”, “make the change step by step”Editing first picks an approach by default. When the hard cases show up, the early work is redone.
    Right helper, wrong unknownAn interview when the unknown is the code; tests first when the approach is undecided; a plan when the unknown is what the user wantsEach helper fixes one kind of unknown. Match it to what you don't know yet.
    Discovery in the main sessionRunning long searches in the planning session, then compacting afterwardsThe output already crowded the session. The Explore subagent keeps it out from the start and returns a summary.

    Practice: three exam-style questions

    Answer first, then open “Think it through”.

    Rule to remember

    Small and settled → just do it. Big or undecided → plan first. Long searches go to the Explore subagent; unclear asks get an interview; known answers become tests.

    Exam guide 3.4: “Plan mode: large-scale changes, multiple valid approaches, architectural decisions, multi-file mods.” “Direct execution: simple well-scoped changes (single validation check).” “Plan mode enables safe exploration/design before committing → prevents rework.” “Explore subagent isolates verbose discovery output, returns summaries.” Exam guide 3.5: “Test-driven iteration (write tests first, share failures); the interview pattern (Claude asks questions first)”.

    ← All traps