Skill · Plan and specify
/plan-review$plan-review@planr-plan-review
Review a plan for product, engineering, design, and developer-experience problems after planning and before anyone builds. You get one verdict and concrete corrections.
/plan-reviewin Claude Code. If /plan-review runs another command, use /planr:plan-review.
$plan-reviewin Codex. With the OpenPlanr plugin for Codex, use $planr:plan-review.
@planr-plan-reviewin Cursor. Cursor applies the planr-plan-review rule when you mention it in chat.
What it does
Review an OpenPlanr plan for product, engineering, design, and developer-experience problems. Use after planning and before implementation to improve the plan.
The review checks that the outcome is clear and measurable, then looks at scope, sequencing, ownership, architecture, migration, security, operability, testing, and rollback in proportion to the change, plus the first-run and everyday developer experience. It uses only the lenses the work needs.
It leads with one verdict: ready, ready with improvements, or needs revision. Then come the issues that must be fixed, the improvements worth making, the open decisions with a recommended default, and the smallest next step, each finding tied to the plan section it affects. See Review before it lands.
When to use it
Use it to
- Review an implementation plan for product, engineering, design, and developer-experience problems
- Challenge a plan before implementation
Not for
- Implement the plan
- Write a new specification from vague intent
Example
/plan-review SPEC-001$plan-review SPEC-001@planr-plan-review SPEC-001Prompts and commands
Check a plan's first-run developer experience
Ask the plan review to focus on setup, defaults, error messages, and recovery.
Check migration and rollback before you build
Have the plan reviewed for migration, security, operability, and rollback risk.
Review a plan before anyone builds it
Catch product, engineering, design, and developer-experience problems before implementation starts.