Plan mode — make it think before it builds
A read-only mode where it can study and propose but cannot touch anything.
Not filmed yet
The lesson is written out below. The video comes after.
The most common expensive failure is not a wrong answer. It is confidently building the wrong thing, beautifully, for twenty minutes.
Plan mode is the fix and it is almost free. It is a read-only state: it can open files, study how something works, and come back with a proposal, but it cannot change anything while it is in there. You read the plan, you correct the two things it misunderstood, and then you let it go.
My rule is that anything I expect to take more than about ten minutes starts there. The thirty seconds of reading a plan is the cheapest insurance in the whole workflow.
The one thing to keep
Anything over ten minutes starts in plan mode.
More in Claude Code
Next to this one
Skills — teach it once and it knows forever
Do the task, get it right, then say "turn what we just did into a skill." The work becomes the training material.
Claude CodeHooks — rules that fire without asking
Automatic tripwires, so the discipline is not left to your memory.
Claude CodeWhy a fresh chat beats a long one
Two reasons — cost and quality — and they both go the same direction.