When to plan and when to just do

Lesson outcome

You will know when to enter plan mode and when to give a direct instruction, and you will understand why getting this wrong is expensive in both directions.

Why this matters in an agency

There are two failure modes with Claude Code. The first is over-planning: entering plan mode for every small task, which turns a 30-second action into a 10-minute ceremony. The second is under-planning: giving Claude Code a complex, multi-step task as a one-shot prompt and hoping it gets everything right. Under-planning is far more costly — it produces output that misses requirements, creates files in wrong locations, or silently ignores edge cases.

The skill is knowing which mode fits the task.

Inputs, tools, and prerequisites

Claude Code running on your VPS or locally. No specific tools needed — this is a mental model lesson with practical exercises.

Step-by-step walkthrough

The decision rule

Use this simple test: if the task has more than two steps or involves any uncertainty, use plan mode.

Examples of direct instruction tasks (no plan needed):

• "Add a line to the Active Client Index for Precision Paving."
• "Read the Reporting SOP and tell me the verification steps."
• "Create a new journal entry for today."
• "What is the cost-per-lead for ABC Paving from the last report?"

These are bounded, clear, and verifiable at a glance.

Examples of plan mode tasks:

• "Build a script that monitors our client websites and alerts us if any go down."
• "Reorganize the vault — clients should be grouped by service type instead of alphabetically."
• "Create a content brief, outline, and first draft for a blog post about local SEO."
• "Audit the Operations folder and identify SOPs that are outdated."

These involve multiple steps, decisions, dependencies, or potential for scope creep.

How plan mode works in Claude Code

Plan mode is a feature built into Claude Code. You activate it by typing /plan or by asking Claude Code to plan before executing:

```
/plan
```

Or:

```
I need to reorganize the vault's client folders. Before making any changes, create a plan that shows what you would move, rename, and restructure. Do not execute anything until I approve.
```

In plan mode, Claude Code reads relevant files, analyzes the situation, and proposes a plan. The plan includes:

• What it will do — specific actions in order
• What it will NOT do — scope boundaries
• Dependencies — what needs to happen first
• Risks — what could go wrong

You review the plan. You can approve it, modify it, or reject it. Only after approval does Claude Code execute.

The cost of skipping plan mode

When you skip plan mode on a complex task, three things happen:

1. Scope drift — Claude Code makes assumptions about what you want, and those assumptions may be wrong. You discover this after the work is done, not before.
2. Missed dependencies — Claude Code may modify a file that depends on another file it has not read. The result looks correct locally but breaks something elsewhere.
3. No verification standard — Without a plan, there is no agreed definition of "done." You cannot verify the work against requirements that were never stated.

Planning takes two to five minutes. Fixing unplanned work takes twenty minutes to an hour. The math is clear.

The cost of over-planning

If you enter plan mode for "add a bullet point to this note," you waste time. Direct instructions are faster for simple tasks. The goal is not to plan everything — it is to plan the right things.

Failure modes and verification checks

The main failure is defaulting to one mode for all tasks. Some people always use direct instructions (and get burned on complex tasks). Others always enter plan mode (and move slowly on simple tasks). Match the mode to the task.

Verification: look at the last five tasks you did with Claude Code. For each one, would plan mode have caught a mistake? Would a direct instruction have saved time? If you can accurately classify each task in hindsight, you have the mental model.

Implementation checklist

• Understand the two-step decision rule (plan mode if 2+ steps or uncertainty).
• Know how to enter plan mode (/plan or explicit instruction).
• Understand the cost of under-planning (scope drift, missed dependencies, no verification).
• Understand the cost of over-planning (wasted time on simple tasks).

Immediate next action

Move to the next lesson and run a real task through the full plan-execute-verify cycle.

Exercise

Classify these ten tasks as "direct instruction" or "plan mode":

1. "Change the phone number in the Agency Overview note." → Direct
2. "Build a lead scoring spreadsheet for our sales pipeline." → Plan
3. "What does the Client Onboarding SOP say about the first call?" → Direct
4. "Create an email sequence for re-engaging inactive leads." → Plan
5. "Delete the test notes we created in Module 2." → Direct
6. "Migrate the report generator to read from an API instead of CSV." → Plan
7. "Add today's journal entry." → Direct
8. "Audit all vault notes and flag any with outdated information." → Plan
9. "Tell me how many notes are in the Clients folder." → Direct
10. "Build a dashboard that shows real-time client metrics." → Plan

If your classifications match, you have the skill. If any are unclear, think about why — the boundary cases are where the judgment matters most.