cpo-review

alirezarezvani/claude-skills · .gemini/skills/cpo-review/SKILL.md

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

Product & ResearchNo license★ 25441⑂ 3598commit 19392f7

Install skillView source on GitHub

What this skill does

/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

Agent: cs-cpo-advisor
Skill: cpo-advisor
Execution: product-team/skills/product-manager-toolkit/

Version: 1.0.0

Installation

Copy a source-pinned command for your client. You run it yourself.

Destination: .claude/skills/cpo-review · pinned to the source commit

# Run from your project root
git clone https://github.com/alirezarezvani/claude-skills.git .skillboard-tmp
git -C .skillboard-tmp checkout 19392f7a08264ed00486a251f5b2098321771f94
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/.gemini/skills/cpo-review" ".claude/skills/"
rm -rf .skillboard-tmp

Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.

New here? Step-by-step setup – from installing the agent to using the skill

Operating systemAgentI already use Claude Code

1
Install Git
Install Git with your package manager (Debian/Ubuntu shown; use dnf/pacman on others). Official download.
```
sudo apt update && sudo apt install -y git
```
2
Install Claude Code
Requires Node.js 18+. Install the CLI globally: Official docs. (command-line tool)
```
npm install -g @anthropic-ai/claude-code
```

Get the skill, pinned to its exact version

Open a terminal and run these steps (they clone the source, check out the exact commit, and copy the skill into place):

# Run from your project root
git clone https://github.com/alirezarezvani/claude-skills.git .skillboard-tmp
git -C .skillboard-tmp checkout 19392f7a08264ed00486a251f5b2098321771f94
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/.gemini/skills/cpo-review" ".claude/skills/"
rm -rf .skillboard-tmp

Destination: .claude/skills/cpo-review

4
Use it in Claude Code
Open Claude Code in your project. It reads skills from the folder above, so cpo-review is now available. Always review the source before using it – static checks cannot prove runtime safety.

Security & Audits

Scanner static-checks@0.1.0 · commit 19392f7a0826. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.

lowPath traversal reference
References parent-directory traversal, which can escape a target directory.
Evidence: ../· fingerprint fa08499e14d0113b

cpo-review

alirezarezvani/claude-skills · .gemini/skills/cpo-review/SKILL.md

Product & ResearchNo license★ 25441⑂ 3598commit 19392f7

Install skillView source on GitHub

What this skill does

/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

Agent: cs-cpo-advisor
Skill: cpo-advisor
Execution: product-team/skills/product-manager-toolkit/

Version: 1.0.0

Installation

Copy a source-pinned command for your client. You run it yourself.

Destination: .claude/skills/cpo-review · pinned to the source commit

# Run from your project root
git clone https://github.com/alirezarezvani/claude-skills.git .skillboard-tmp
git -C .skillboard-tmp checkout 19392f7a08264ed00486a251f5b2098321771f94
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/.gemini/skills/cpo-review" ".claude/skills/"
rm -rf .skillboard-tmp

Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.

New here? Step-by-step setup – from installing the agent to using the skill

Operating systemAgentI already use Claude Code

1
Install Git
Install Git with your package manager (Debian/Ubuntu shown; use dnf/pacman on others). Official download.
```
sudo apt update && sudo apt install -y git
```
2
Install Claude Code
Requires Node.js 18+. Install the CLI globally: Official docs. (command-line tool)
```
npm install -g @anthropic-ai/claude-code
```

Get the skill, pinned to its exact version

Open a terminal and run these steps (they clone the source, check out the exact commit, and copy the skill into place):

# Run from your project root
git clone https://github.com/alirezarezvani/claude-skills.git .skillboard-tmp
git -C .skillboard-tmp checkout 19392f7a08264ed00486a251f5b2098321771f94
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/.gemini/skills/cpo-review" ".claude/skills/"
rm -rf .skillboard-tmp

Destination: .claude/skills/cpo-review

4
Use it in Claude Code
Open Claude Code in your project. It reads skills from the folder above, so cpo-review is now available. Always review the source before using it – static checks cannot prove runtime safety.

Security & Audits

Scanner static-checks@0.1.0 · commit 19392f7a0826. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.

lowPath traversal reference
References parent-directory traversal, which can escape a target directory.
Evidence: ../· fingerprint fa08499e14d0113b

cpo-review

What this skill does

/cs:cpo-review — CPO Forcing Questions

When to Run

The Six CPO Questions

1. JTBD

2. North Star Metric

3. PMF Signal

4. RICE Score

5. Opportunity Cost

6. Kill Criteria

Workflow

Output Format

Routing

Related

Installation

Install Git

Install Claude Code

Get the skill, pinned to its exact version

Use it in Claude Code

Security & Audits

cpo-review

What this skill does

/cs:cpo-review — CPO Forcing Questions

When to Run

The Six CPO Questions

1. JTBD

2. North Star Metric

3. PMF Signal

4. RICE Score

5. Opportunity Cost

6. Kill Criteria

Workflow

Output Format

Routing

Related

Installation

Install Git

Install Claude Code

Get the skill, pinned to its exact version

Use it in Claude Code

Security & Audits