/cs:cpo-review — CPO Forcing Questions
/cs:cpo-review <plan> — JTBD-driven interrogation of product roadmap, PMF signal, and portfolio focus.
How to use it
Claude Code
- Run the line below. It pulls the whole folder into
~/.claude/skills/cpo-review. - Describe your job in plain words. Claude Code follows the skill from there.
Claude Code — installs the whole folder, not just SKILL.md
npx degit alirezarezvani/claude-skills/c-level-agents/skills/cpo-review#main ~/.claude/skills/cpo-reviewFor one project only, change the path to .claude/skills/cpo-review.
Claude (web or desktop app)
- On this page open ⋯ → Download .md.
- Save it as SKILL.md in a folder, zip the folder, then Customize → Skills → + → Create skill → Upload a skill.
- Pick the file and Save. Claude shows the name and description and runs a security scan.
- Check the skill is switched on.
- Start a new chat and describe your job in plain words. The AI follows the skill from there.
ChatGPT or another app
- ChatGPT: make a Project and paste it into Instructions.
- Neither? Paste it at the top of a new chat — it works for that chat.
Not working?
- Check which app you pasted it into — the steps above name the right one.
- Some skills need the paid tier of Claude or ChatGPT.
Paste into Claude, ChatGPT or Cursor.
Source of /cs:cpo-review — CPO Forcing Questions
Show the full text111 lines
| name | description |
|---|---|
| cpo-review | /cs:cpo-review <plan> — JTBD-driven interrogation of product roadmap, PMF signal, and portfolio focus. Use when committing a quarter's roadmap, deciding whether to kill a feature, or claiming PMF without a retention curve. |
/cs:cpo-review — CPO Forcing Questions
Command: /cs: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
- Run the analyses:
python ../../../c-level-advisor/skills/cpo-advisor/scripts/pmf_scorer.py python ../../../c-level-advisor/skills/cpo-advisor/scripts/portfolio_analyzer.py - Answer the six questions.
- 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
/cs:cmo-review— does the positioning support this feature?/cs:execute— build the 90-day plan/cs:post-mortem— if kill criteria triggered
Related
- Agent:
cs-cpo-advisor - Skill:
cpo-advisor - Execution:
product-team/skills/product-manager-toolkit/
Version: 1.0.0
| 1 | |
| 2 | name "cpo-review" |
| 3 | description "/cs:cpo-review <plan> — JTBD-driven interrogation of product roadmap, PMF signal, and portfolio focus. Use when committing a quarter's roadmap, deciding whether to kill a feature, or claiming PMF without a retention curve." |
| 4 | |
| 5 | |
| 6 | # /cs:cpo-review — CPO Forcing Questions |
| 7 | |
| 8 | **Command:** `/cs:cpo-review <plan>` |
| 9 | |
| 10 | The JTBD-driven builder cuts the roadmap in half. Six questions to surface what to ship and what to kill. |
| 11 | |
| 12 | ## When to Run |
| 13 | |
| 14 | Before quarterly roadmap commitment |
| 15 | Before launching a new product line |
| 16 | Before adding > 3 features to a release |
| 17 | When retention is flat or declining |
| 18 | When the team is debating "should we build X?" |
| 19 | |
| 20 | ## The Six CPO Questions |
| 21 | |
| 22 | ### 1. JTBD |
| 23 | **What job is this feature hired to do, in the user's words?** |
| 24 | Not "improve onboarding." "Help a new ops manager get their first deal closed within 7 days." |
| 25 | Job ≠ feature. Hire ≠ try. |
| 26 | |
| 27 | ### 2. North Star Metric |
| 28 | **What user behavior does this move, and how does that ladder to the North Star?** |
| 29 | The metric must be leading, behavior-based, and value-correlated. |
| 30 | If you can't trace the feature to the North Star, don't build it. |
| 31 | |
| 32 | ### 3. PMF Signal |
| 33 | **What's the retention curve for users who hire this job — is it flat, decaying, or smiling?** |
| 34 | Flat or smiling = PMF signal. Decaying = no PMF. |
| 35 | "Users like it in surveys" is not a signal. |
| 36 | |
| 37 | ### 4. RICE Score |
| 38 | **Reach, Impact, Confidence, Effort — what's the score and where does this rank in the queue?** |
| 39 | |
| 40 | python product-team/skills/product-manager-toolkit/scripts/rice_prioritizer.py |
| 41 | |
| 42 | |
| 43 | ### 5. Opportunity Cost |
| 44 | **What gets cut if this ships? Name the specific initiative or feature.** |
| 45 | Headcount and time are zero-sum. The cut list is the focus list. |
| 46 | |
| 47 | ### 6. Kill Criteria |
| 48 | **What signal would tell you in 90 days that this was the wrong bet?** |
| 49 | Define the metric and threshold in writing, before launch. |
| 50 | If you can't define a kill criterion, you can't ship responsibly. |
| 51 | |
| 52 | ## Workflow |
| 53 | |
| 54 | **Run the analyses:** |
| 55 | |
| 56 | python ../../../c-level-advisor/skills/cpo-advisor/scripts/pmf_scorer.py |
| 57 | python ../../../c-level-advisor/skills/cpo-advisor/scripts/portfolio_analyzer.py |
| 58 | |
| 59 | **Answer the six questions.** |
| 60 | **Apply the verdict.** |
| 61 | |
| 62 | ## Output Format |
| 63 | |
| 64 | |
| 65 | # CPO Review: <feature/plan> |
| 66 | **Date:** YYYY-MM-DD |
| 67 | |
| 68 | ## JTBD |
| 69 | > <one sentence in user voice> |
| 70 | |
| 71 | ## North Star Link |
| 72 | - Metric moved: <name> |
| 73 | - Expected delta: <%> |
| 74 | |
| 75 | ## PMF Signal |
| 76 | - Retention curve shape: flat / smiling / decaying |
| 77 | - Cohort sample size: N |
| 78 | |
| 79 | ## Score |
| 80 | - RICE: <number> |
| 81 | - Rank in queue: #N of M |
| 82 | |
| 83 | ## Cut List |
| 84 | - Cut: <initiative> |
| 85 | - Reason: <why this matters more> |
| 86 | |
| 87 | ## Kill Criteria (90 days) |
| 88 | - Metric: <name> |
| 89 | - Threshold: <value> |
| 90 | - Action if missed: <kill | iterate> |
| 91 | |
| 92 | ## Verdict |
| 93 | 🟢 SHIP | 🟡 SHARPEN | 🔴 KILL |
| 94 | |
| 95 | |
| 96 | ## Routing |
| 97 | |
| 98 | `/cs:cmo-review` — does the positioning support this feature? |
| 99 | `/cs:execute` — build the 90-day plan |
| 100 | `/cs:post-mortem` — if kill criteria triggered |
| 101 | |
| 102 | ## Related |
| 103 | |
| 104 | Agent: [`cs-cpo-advisor`] |
| 105 | Skill: [`cpo-advisor`] |
| 106 | Execution: `product-team/skills/product-manager-toolkit/` |
| 107 | |
| 108 | |
| 109 | |
| 110 | **Version:** 1.0.0 |
| 111 |
Discussion
🏛️ Tax Strategist AgentExpert tax strategist specializing in tax optimization, multi-jurisdictional compliance, transfer pricing, and strategic tax planning. Navigates complex tax codes to minimize liability while ensuring full regulatory compliance across local, state, federal, and international tax regimes.📈 FP&A Analyst AgentExpert Financial Planning & Analysis (FP&A) analyst specializing in budgeting, variance analysis, financial planning, rolling forecasts, and strategic decision support. Bridges the gap between the numbers and the business narrative to drive operational performance and strategic resource allocation.📊 Financial Analyst AgentExpert financial analyst specializing in financial modeling, forecasting, scenario analysis, and data-driven decision support. Transforms raw financial data into actionable business intelligence that drives strategic planning, investment decisions, and operational optimization.Career changer translatorTranslate skills from one industry to another, identify transferable skills
Browse more free Claude skills or everything in Product.