[FEATURE] Add "Review plan for gaps" option before plan execution

Resolved 💬 3 comments Opened Jan 24, 2026 by lazyants Closed Feb 28, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

Problem

When Claude finishes generating a plan in plan mode, users see this menu:

Would you like to proceed?

❯ 1. Yes, clear context and auto-accept edits (shift+tab)
   2. Yes, auto-accept edits
   3. Yes, manually approve edits
   4. Type here to tell Claude what to change

There's no option for Claude to self-review the plan before execution. Users who want Claude to critique its own plan must manually type something like "review your plan for gaps first" — breaking the flow.

Why This Matters

Claude often jumps into implementation without catching:

  • Missing edge cases
  • Unvalidated assumptions
  • Dependency ordering issues
  • Error handling gaps

These issues are cheapest to fix before any code is written. The plan approval moment is the ideal checkpoint.

Proposed Solution

Proposed Solution

Add a new menu option:

Would you like to proceed?

❯ 1. Yes, clear context and auto-accept edits (shift+tab)
   2. Yes, auto-accept edits
   3. Yes, manually approve edits
   4. Review plan for gaps first   ← NEW
   5. Type here to tell Claude what to change

Selecting option 4 would prompt Claude to:

  1. Re-read its plan
  2. Identify potential gaps, edge cases, or assumptions
  3. Present findings to the user
  4. Return to the approval menu (possibly with a revised plan)

Why Not Automatic Review?

  • Adds latency/cost to every plan, even simple ones
  • Risk of endless loops (find issue → revise → review → find another issue...)
  • User should decide when the extra step is worth it

A manual option keeps the user in control.

Summary

The plan approval menu is the perfect moment for optional self-review. Adding this option would catch issues at the cheapest possible point — before implementation begins — without forcing overhead on simple tasks.

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

Interactive mode (TUI)

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗