Have a second Claude session review the plan before coding
Write the plan in one session, then open a fresh Claude with no context and ask it to review the plan like a staff engineer.
The problem
The same session that drafted the plan is biased toward it, so gaps and riskier steps slip through.
The hack
After plan mode produces a design, start a new Claude session, paste only the plan, and ask for a critical review before implementation.
Why it works
A cold second session has no sunk-cost bias. It catches missing edge cases, verification steps, and over-scoped work before you burn tokens coding.
Setup
1. Use plan mode (`Shift+Tab` twice) to produce a written plan. 2. Optionally edit it with `Ctrl+G`. 3. Open a fresh Claude session (or worktree). 4. Paste the plan and ask: “Review as a staff engineer. List gaps, risks, and missing verification steps. Do not implement.” 5. Merge feedback into the plan, then implement.
Prompt
Review this plan as a staff engineer. List gaps, risks, and missing verification. Do not implement yet.
Discussion
No comments yet. Be the first to say whether this worked for you.