| name | plan-eng-review |
| description | Engineering-manager style implementation plan review. Use when asked to review architecture, lock in an execution plan, assess data flow, edge cases, test coverage, performance, rollout risk, or perform an engineering review before coding. |
Plan Eng Review
Overview
Review an implementation plan before coding. The goal is to catch architecture risks, missing contracts, test gaps, and over/under-engineering while the plan is still cheap to change.
Review Workflow
- Read the target plan and relevant project docs.
- Restate the goal and scope in plain language.
- Check architecture and data flow.
- Check ownership boundaries, contracts, and dependencies.
- Check edge cases, failure modes, security, performance, and rollback.
- Check test strategy and smoke coverage.
- Produce opinionated recommendations with priority.
- If requested, update the plan with accepted recommendations.
Review Standards
Prefer:
- explicit contracts over implicit coupling
- boring technology over clever abstractions
- incremental changes over big-bang rewrites
- deterministic tests over manual-only confidence
- minimal diff with enough edge-case coverage
Flag:
- shared files with unclear owners
- stubs without follow-up path
- tests that only cover happy paths
- hidden migration or rollout risks
- plans that mix unrelated features
- scope creep disguised as cleanup
Output Shape
Use this compact structure:
- Verdict: ready / needs revision / blocked
- Top risks
- Architecture and contract notes
- Test coverage notes
- Required plan edits
- Recommended next action
Read references/eng-review-checklist.md for a full checklist when needed.
