| name | lazy-plan-reviewer |
| description | Critically review technical plan documents (PLAN-*.md) against the current codebase before implementation. Use when asked to review a plan, validate a plan, check a plan for issues, audit an implementation plan, or assess whether a plan is ready to implement. Catches design flaws, codebase mismatches, and risky assumptions. |
Lazy Plan Reviewer
Review plan documents against the codebase before implementation to catch design flaws, mismatches, and risky assumptions.
Review Process
- Load plan context — Read plan file, identify goals, architecture, assumptions
- Check repo state —
git status, git branch -vv, git log --oneline -20
- Plan vs codebase alignment — Map plan items to existing code, check feasibility
- Architecture critique — Evaluate modularity, coupling, backwards compatibility
- Risk assessment — Security, performance, migration complexity
- Implementation readiness — Milestones, test coverage, validation criteria
Focus Areas
Critical (Must Fix)
- Conflicts with existing codebase
- Security/data integrity risks
- Breaking changes without migration strategy
- Infeasible or underestimated changes
Important (Should Fix)
- Vague requirements
- Misaligned architecture patterns
- Unclear module boundaries
- Missing performance considerations
Suggestions (Nice to Fix)
- Plan clarity and structure
- Additional diagrams/examples
- Documentation improvements
Output Format
## Plan Review Summary
[Overall assessment of feasibility]
## Critical Issues
- [Issue with file:line reference]
- [Recommendation]
## Important Issues
- [Issue with reference]
- [Suggested fix]
## Suggestions
- [Non-blocking improvements]
## Codebase Alignment
- [Plan section] -> [Relevant files]
- [Gaps where no mapping exists]
## Approval Status
**READY TO IMPLEMENT** / **NEEDS REVISION**
Guidelines
- Reference specific plan sections and code locations (
path/file.ext:line)
- Propose actionable alternatives, not just problems
- Prioritize by real-world risk and implementation cost
- Use
ask_questions tool for ambiguous sections or critical decisions
Usage
Provide the plan file path, or run without arguments to auto-detect PLAN-*.md files in the project root.
