Percerno Skillsbeta
← everything it can do · finance

Cpo Review TEXT

Performs a rigorous CPO-level review of a product plan or feature using six forcing questions (JTBD, North Star, PMF, RICE, Opportunity Cost, Kill Criteria) to determine if it should be shipped, refined, or killed.

4 uses this weeksource alirezarezvanilicence MIT
Quality gate: PASS · better answers · measured 2026-10-23
Blind-judged against the bare model on 2 requests: average lift +4.5 points (specificity, structure, method, fit).
won 2/2, lift +4.5, tokens ×52.15
Security scan: clean · 2026-10-24 · 1 files · ran in sandbox
no network calls, shell tricks, credential access or instruction tampering found in its files.

Try asking

Say it in your own words; the assistant finds this recipe by itself. Examples:

“Gennemgå vores Q4 roadmap før vi godkender den til næste kvartal.”
“Skal vi dræbe den nye rapporteringsfunktion? Retentionen er flad de sidste 3 måneder.”
“Kør en CPO-review på forslaget i filen 'ny-feature-spec.md'.”
“Review our Q3 roadmap plan before we lock it in next week.”
“Should we kill the new onboarding flow? Retention is dropping after week 2.”
“Run a CPO review on the 'AI Assistant' feature proposal in docs/ai-assistant.md.”
Try this skill from Claude, ChatGPT or a chat on your own page. Free plan, no credit card.Get started free

Good for

product-managementroadmap-reviewjtbdpmf-analysisfeature-evaluationstrategic-planningrice-scoringdecision-making

Not for

Do not use this for general marketing positioning reviews (use cmo-review) or for creating detailed 90-day execution plans (use execute). It is not for post-launch failure analysis (use post-mortem) or for technical architecture reviews.

Details

When it is the right choice

Use this skill when committing to a quarterly roadmap, evaluating whether to launch a new feature, or investigating flat retention metrics. It is ideal for resolving debates about feature priority by forcing a clear definition of user jobs and kill criteria. It is also appropriate when a team claims Product-Market Fit without supporting retention data.

The full recipe the assistant reads

/c-level-agents:cpo-review — CPO Forcing Questions

Command: /c-level-agents:cpo-review <plan>

The JTBD-driven builder cuts the roadmap in half. Six questions to surface what to ship and what to kill.

When to Run

  • Before quarterly roadmap commitment
  • Before launching a new product line
  • Before adding > 3 features to a release
  • When retention is flat or declining
  • When the team is debating "should we build X?"

The Six CPO Questions

1. JTBD

What job is this feature hired to do, in the user's words? - Not "improve onboarding." "Help a new ops manager get their first deal closed within 7 days." - Job ≠ feature. Hire ≠ try.

2. North Star Metric

What user behavior does this move, and how does that ladder to the North Star? - The metric must be leading, behavior-based, and value-correlated. - If you can't trace the feature to the North Star, don't build it.

3. PMF Signal

What's the retention curve for users who hire this job — is it flat, decaying, or smiling? - Flat or smiling = PMF signal. Decaying = no PMF. - "Users like it in surveys" is not a signal.

4. RICE Score

Reach, Impact, Confidence, Effort — what's the score and where does this rank in the queue?

python product-team/skills/product-manager-toolkit/scripts/rice_prioritizer.py

5. Opportunity Cost

What gets cut if this ships? Name the specific initiative or feature. - Headcount and time are zero-sum. The cut list is the focus list.

6. Kill Criteria

What signal would tell you in 90 days that this was the wrong bet? - Define the metric and threshold in writing, before launch. - If you can't define a kill criterion, you can't ship responsibly.

Workflow

  1. Run the analyses: bash python ${CLAUDE_PLUGIN_ROOT}/vendor/c-level-advisor/cpo-advisor/scripts/pmf_scorer.py python ${CLAUDE_PLUGIN_ROOT}/vendor/c-level-advisor/cpo-advisor/scripts/portfolio_analyzer.py
  2. Answer the six questions.
  3. Apply the verdict.

Output Format

# CPO Review: <feature/plan>
**Date:** YYYY-MM-DD

## JTBD
> <one sentence in user voice>

## North Star Link
- Metric moved: <name>
- Expected delta: <%>

## PMF Signal
- Retention curve shape: flat / smiling / decaying
- Cohort sample size: N

## Score
- RICE: <number>
- Rank in queue: #N of M

## Cut List
- Cut: <initiative>
- Reason: <why this matters more>

## Kill Criteria (90 days)
- Metric: <name>
- Threshold: <value>
- Action if missed: <kill | iterate>

## Verdict
🟢 SHIP | 🟡 SHARPEN | 🔴 KILL

Routing

  • /c-level-agents:cmo-review — does the positioning support this feature?
  • /c-level-agents:execute — build the 90-day plan
  • /c-level-agents:post-mortem — if kill criteria triggered

Related

Version: 1.0.0

Files in this skill (2)
  • LICENSE
  • SKILL.md
Where it comes from

Vendored from alirezarezvani/claude-skills, commit 27cfcd0fb0a4, path c-level-agents/skills/cpo-review, licence MIT. The upstream licence file ships inside the skill.