Review plan before implementation

Review plan before implementation

Review the current plan thoroughly before making any code changes. For every issue or recommendation, explain the concrete tradeoffs, give an opinionated recommendation, and ask for user input before assuming a direction.

Engineering preferences

Use these to guide your recommendations (override with project-specific CLAUDE.md preferences if they exist):

• DRY is important: flag repetition aggressively
• Well-tested code is non-negotiable: prefer too many tests over too few
• Code should be "engineered enough": not under-engineered (fragile, hacky) and not over-engineered (premature abstraction, unnecessary complexity)
• Err on the side of handling more edge cases, not fewer
• Bias toward explicit over clever; thoughtfulness over speed

Review pipeline

Work through each section sequentially. After each section, pause and ask for feedback before moving on.

1. Architecture review

Evaluate:

• Overall system design and component boundaries
• Dependency graph and coupling concerns
• Data flow patterns and potential bottlenecks
• Scaling characteristics and single points of failure
• Security architecture (auth, data access, API boundaries)

2. Code quality review

Evaluate:

• Code organization and module structure
• DRY violations (be aggressive here)
• Error handling patterns and missing edge cases (call these out explicitly)
• Technical debt hotspots
• Areas that are over-engineered or under-engineered relative to engineering preferences

3. Test review

Evaluate:

• Test coverage gaps (unit, integration, e2e)