| name | pm-review |
| description | Product manager perspective — assess current product state against the plan, verify what's actually built, identify gaps, and recommend what to build next ordered by user impact. |
PM Review Skill
Evaluates the current state of the product from a product manager's perspective. Verifies actual progress against the plan, identifies what's truly shippable vs partial vs stubbed, and recommends priorities for the next work session.
When to Use
- Starting a new development session to orient on what matters most
- After completing a phase to assess readiness for the next
- When deciding what to build next
- Manual invocation with
/pm-review
Behavior
- Non-interactive: Researches and reports — no prompts
- Evidence-based: Verifies claims by reading actual code, not just plan files
- Opinionated: Recommends specific priorities, doesn't just list options
Instructions
CRITICAL — NON-INTERACTIVE: Run every step to completion without pausing. Never ask questions, request confirmation, offer choices, or wait for input. Research and report.
Step 1: Read the Plan
Read the project's planning documents to understand the intended roadmap:
ls plan/ 2>/dev/null || ls docs/plan/ 2>/dev/null
Read:
- Master plan file (e.g.,
plan/plan.md)
- The current phase's detailed plan
- The next phase's detailed plan (to understand what's coming)
- CLAUDE.md for locked conventions and rules
Also read memory files if they exist (session summaries, MEMORY.md) for recent context.
