What problem does it solve?
Product teams often commit quarterly roadmaps without validating whether features map to real user jobs, retention signals, or portfolio trade-offs, leading to bloated releases and features that should have been killed.
Core Features & Use Cases
- Six Forcing Questions: Evaluates any plan against JTBD, North Star metric linkage, PMF retention signal, RICE score, opportunity cost, and 90-day kill criteria.
- Structured Verdict Output: Produces a markdown review document ending in a SHIP, SHARPEN, or KILL verdict with a named cut list.
- Script Integration: Invokes pmf_scorer.py and portfolio_analyzer.py from the cpo-advisor skill plus rice_prioritizer.py from the product-manager-toolkit for quantitative backing.
- Use Case: Before committing a quarterly roadmap, run /cs:cpo-review on the plan to force explicit kill criteria and identify which initiative gets cut if a new feature ships.
Quick Start
Run /cs:cpo-review on my Q3 roadmap plan to evaluate each feature against JTBD, PMF signal, and RICE scoring.