New: Earn 20% as an AgentAlley affiliate. Share your link and earn on every sale you refer. Join now New: Earn 20% as an affiliate. Join now

/cs:cpo-review <plan

/cs:cpo-review — CPO Forcing Questions

by alirezarezvani · MIT license · ★ 26,349 on GitHub · updated Aug 30

/cs:cpo-review — CPO Forcing Questions cover

/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.

---
name: "cpo-review"
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."
---

# /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?"

Overview

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

Manual install (npx, ZIP)
Claude Codenpx skills add alirezarezvani/claude-skills --skill cpo-review -g -a claude-code
Claude Code (manual)mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/alirezarezvani/claude-skills/tar.gz/19392f7a0826 \ | tar -xz -C ~/.claude/skills --strip-components=3 claude-skills-19392f7a0826/c-level-agents/skills/cpo-review
Windows (PowerShell)New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/b89c8bc4f4e7f7d3d0c7/cpo-review.zip" -OutFile "$env:TEMP\cpo-review.zip"; Expand-Archive "$env:TEMP\cpo-review.zip" -DestinationPath "$HOME\.claude\skills" -Force
Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md3.1 KB
Read the files here
alirezarezvani/19392f71 file
Shared references5SKILL.md reads these from elsewhere in the repo. Not in the ZIP.Get them on GitHub ↗
SKILL.md
Show the full text111 lines

/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

  1. 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
    
  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

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

Version: 1.0.0

1---
2name: "cpo-review"
3description: "/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 
10The 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```bash
40python 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 
541. **Run the analyses:**
55 ```bash
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 ```
592. **Answer the six questions.**
603. **Apply the verdict.**
61 
62## Output Format
63 
64```markdown
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`](../../agents/cs-cpo-advisor.md)
105- Skill: [`cpo-advisor`](../../../c-level-advisor/skills/cpo-advisor/SKILL.md)
106- Execution: `product-team/skills/product-manager-toolkit/`
107 
108---
109 
110**Version:** 1.0.0
111 
View all files on GitHub →

Details

Updated
Aug 30, 2026
License
MIT
Stars on the repo
★ 26,349
Checked
Source
alirezarezvani/claude-skills ↗
Creator
alirezarezvani · 363 listings
View creator

Similar skills

See all →
MCP3-5 days | Agents: 6 | Gate Keepers: DevOps Automator +⚙️ Phase 2 Playbook — Foundation & Scaffoldingmsitarzewski/agency-agents · by msitarzewski> Duration: 3-5 days | Agents: 6 | Gate Keepers: DevOps Automator + Evidence Collector★ 154k GitHub starsMCPNEXUS transforms The Agency's independent AI specialists🌐 NEXUS — Network of EXperts, Unified in Strategymsitarzewski/agency-agents · by msitarzewski> NEXUS transforms The Agency's independent AI specialists into a synchronized intelligence network. This is not a prompt collection — it…★ 154k GitHub starsSkillGenerate an Ansoff Matrix analysis mapping growth strategiesphuryn/pm-skills · by phurynGenerate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.★ 26.6k GitHub starsSkillSurvey any codebase as a senior advisorImproveshadcn/improve · by shadcnSurvey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on source code — never implements, fixes, or refactors anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX), suggest features or where to take the project next (roadmap, product direction), or generate handoff plans for another agent to implement.★ 9.2k GitHub starsSkillTranslate skills from one industry to anotherCareer changer translatorParamchoudhary/ResumeSkills · by ParamchoudharyTranslate skills from one industry to another, identify transferable skills★ 2.4k GitHub starsSkillA collection of 37 battle-tested marketing skillsOpenClaw Marketing SkillsLeoYeAI/openclaw-marketing-skills · by LeoYeAIA collection of 37 battle-tested marketing skills for OpenClaw agents. Use when you want to install or reference any marketing skill including: CRO (page-cro, signup-flow-cro, onboarding-cro, form-cro, popup-cro, paywall-upgrade-cro), copywriting, copy-editing, cold-email, email-sequence, social-content, seo-audit, ai-seo, programmatic-seo, site-architecture, schema-markup, content-strategy, paid-ads, ad-creative, ab-test-setup, analytics-tracking, referral-program, free-tool-strategy, churn-prevention, revops, sales-enablement, launch-strategy, pricing-strategy, competitor-alternatives, marketing-ideas, marketing-psychology, lead-magnets, product-marketing-context, and data connectors (google-ads-connect, search-console-connect, meta-ads-connect, x-twitter-connect). Start with product-marketing-context to set up your product context document, then use any other skill naturally. Powered by MyClaw.ai.★ 1k GitHub stars

More from alirezarezvani

SkillResume a paused experiment/ar:ar-resume — Resume Experimentalirezarezvani/claude-skills · by alirezarezvaniResume a paused experiment. Checkout the experiment branch, read results history, continue iterating. Use when the user runs /ar:ar-resume or asks to pick up a previously started autoresearch experiment.★ 26.3k GitHub starsSkillShow experiment dashboard with results, active loops/ar:ar-status — Experiment Dashboardalirezarezvani/claude-skills · by alirezarezvaniShow experiment dashboard with results, active loops, and progress. Use when the user runs /ar:ar-status or asks how an autoresearch experiment is going.★ 26.3k GitHub starsSkillStart an autonomous experiment loop with user-selected/ar:loop — Autonomous Experiment Loopalirezarezvani/claude-skills · by alirezarezvaniStart an autonomous experiment loop with user-selected interval (10min, 1h, daily, weekly, monthly). Uses CronCreate for scheduling. Use when the user runs /ar:loop or asks to run an autoresearch experiment continuously on a schedule.★ 26.3k GitHub starsSkillRun a single experiment iteration/ar:run — Single Experiment Iterationalirezarezvani/claude-skills · by alirezarezvaniRun a single experiment iteration. Edit the target file, evaluate, keep or discard. Use when the user runs /ar:run or asks for one manual autoresearch iteration.★ 26.3k GitHub starsSkillSet up a new autoresearch experiment interactively/ar:setup — Create New Experimentalirezarezvani/claude-skills · by alirezarezvaniSet up a new autoresearch experiment interactively. Collects domain, target file, eval command, metric, direction, and evaluator. Use when the user runs /ar:setup or asks to start optimizing a file with the autoresearch loop.★ 26.3k GitHub starsSkill/cs:boardroom <brief/cs:boardroom — Multi-Role Boardroom Deliberationalirezarezvani/claude-skills · by alirezarezvani/cs:boardroom <brief> — 6-phase multi-role deliberation across the C-suite with Phase 2 isolation, critic pre-screen, and synthesis. Outputs a board memo. Use when a decision spans multiple executive domains — e.g. a pricing change touching finance, positioning, and product, or a raise-vs-cut runway call.★ 26.3k GitHub stars