plan-review
Installation
SKILL.md
Plan review
Use this skill when
- The user asks for an implementation plan, rollout plan, migration plan, or a hardened revision of an existing plan
- The user is already planning or wants review-gated planning before implementation begins
- The user wants named reviewer models or agents to approve the plan
- The user explicitly asks for reviewer-gated or multi-round approval, Jason/Freddy-style review, or
[PLAN-APPROVED]/[PLAN-REVISE-NEEDED]verdict tokens on an existing plan - The user wants stronger plan quality checks around repo fit, feasibility, validation, rollout safety, or scope control
Do not use this skill when
- The main task is reviewing finished code, a diff, or merge readiness; use
implementation-reviewinstead - The user only wants a contract-shaped brief or definition of done with no plan artifact; use
reverse-promptif explicit success and failure framing is the main output - The user explicitly wants immediate implementation with no planning artifact or review gate
- The user wants the larger Research → Plan → Implement → Validate operating model; use
rpi-workflowinstead