Review Implementation Plans

Review implementation plan for gaps, bugs, simplifications, and better approaches

Design review before implementation when architectural fit, edge cases, and code reuse must be vetted before work starts.

• · Plan file or description from $ARGUMENTS

• · Four-axis review: simplification opportunities, gaps/missing items, potential bugs, better approaches
• · Actionable feedback with codebase context and references
• · Code snippets showing recommended patterns

• · Read (plan file, codebase files)
• · Grep (find existing utilities)
• · WebFetch (docs if needed)

• · Plan file readable (markdown or text)
• · Codebase accessible for context
• · ./docs/ folder for architectural guidance

• · Plan too vague = review at high level, missing specific issues
• · No codebase context = recommendations don't fit project patterns
• · docs/ folder empty = architectural review limited
• · Plan is just braindump = review difficult, suggest refining first

• · Checks for existing utilities before proposing new code
• · References ./docs/ for architectural patterns
• · Distinguishes simplification from scope change
• · Cites specific line-of-code impacts for each recommendation