cpo-review

Interrogates product roadmaps with six JTBD-driven questions to decide what to ship or kill.

25.3k|3.6k|Updated Oct 19, 2025
One-click install
npx skills add https://github.com/alirezarezvani/claude-skills --skill cpo-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cpo-review
Source: https://github.com/alirezarezvani/claude-skills/tree/main/c-level-agents/skills/cpo-review
Command: npx skills add https://github.com/alirezarezvani/claude-skills --skill cpo-review

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about cpo-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decide which features to cut from a product roadmap?

Run the six CPO questions against each feature: define its JTBD in user words, trace it to a North Star metric, check the retention curve shape, compute a RICE score, name what gets cut if it ships, and set 90-day kill criteria before launch.

How to evaluate product-market fit signal for a feature?

Examine the retention curve for users who hire the feature's job: flat or smiling curves indicate PMF signal, while decaying curves indicate no PMF. Survey responses and stated preferences do not count as valid signals.

What is a RICE score and how is it used in roadmap prioritization?

RICE combines Reach, Impact, Confidence, and Effort into a single prioritization score. The review workflow runs rice_prioritizer.py from the product-manager-toolkit to compute the score and rank the feature within the queue.

When should I run a CPO review on a product plan?

Run it before quarterly roadmap commitments, before launching a new product line, before adding more than three features to a release, when retention is flat or declining, or when the team debates whether to build something.

What are kill criteria in product management?

Kill criteria are a predefined metric and threshold, written before launch, that signal within 90 days whether a bet was wrong. If the threshold is missed, the team executes a documented kill or iterate action.