Cpo Review
/cs:cpo-review <plan> — JTBD-driven interrogation of product roadmap, PMF signal, and portfolio focus.
Before & after
Same prompt, same agent — the only difference is the skill.
Let me review your roadmap for you. It looks like you have some good features planned. You'll want to make sure your roadmap aligns with what customers actually need. PMF is important—you should look at retention to understand if you have product-market fit. Customer feedback is valuable too. Do you have any retention data or usage metrics I could look at? That would help me give you better feedback on whether these features make sense.
ROADMAP VALIDATION: JTBD + PMF Audit CUSTOMER JOBS (Not features) Extract from support tickets, interviews, churn surveys: Job 1: "I need to close deals faster without losing data in the handoff between sales and CS" → Roadmap alignment: Feature X (CRM integration) ✓ addresses this directly → Test: 80% of churned customers mention handoff friction? If <20%, this job is invented Job 2: "I want to see trends over 6-month windows to predict churn before it happens" → Roadmap alignment: Feature Y (analytics dashboard) partially addresses (3-month window only) → Gap: Annual trends feature not planned; misses customer job PMF VALIDATION (Retention Curve) Pull cohort retention from last 6 months: • Month 0 (churn): Expect 40-50% (normal) • Month 2: Expect >60% (PMF signal: retention inflection, users depend on product) • Month 6: Your data shows 51% (weak PMF signal; retention flat-lining, not sticky) Risk: Roadmap assumes PMF is proven and focuses on expansion features (job creation, automation). If Month 6 retention is 51%, you're fixing the wrong layer. You need retention fixes first. THE TRAP: Feature Factory Q3 roadmap has 6 new features, 2 integrations, 1 performance optimization. None directly target retention cohorts that are leaking customers. → Likely outcome: Launch features, retention stays 51%, burn rate increases PRIORITY REORDER (JTBD-driven) BEFORE building expansion features: 1. Identify 2-3 customer jobs that predict retention (survey churned users) 2. Measure: Do retained users complete these jobs faster/easier than churned users? 3. Only if yes → dedicate 50% Q3 engineering to nailing these jobs 4. Remaining 50% → planned roadmap (expansion) GO/NO-GO GATES ☐ Retention cohort Month 6 reaches 65% (or explain why 51% is acceptable) ☐ Top 3 churn reasons documented + roadmap items trace to each ☐ Feature validation: Test with 5 customers before building (not after) ☐ Metrics dashboard: Track retention by feature usage (not just overall cohort) FINAL CALL: Roadmap is not validated against PMF. De-risk by validating retention first.
About this skill
name: cpo-review description: Use when /cs:cpo-review <plan> — JTBD-driven interrogation of product roadmap, PMF signal, and portfolio focus.
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.
What you get
- Public GitHub repo (alirezarezvani/claude-skills)
- the cpo-review skill folder with SKILL.md. Part of a 337-skill / 30-agent / 70-command install.
Customize your output
- Fork the repo and adapt the skill's instructions and references to your workflow.
Example output
Activates automatically when your request matches Cpo Review; chains with the other skills, agents, and commands in the collection.
Best for
Creators, builders, and teams using Claude Code.
SKILL.md preview
---
name: cpo-review
description: Use this skill when committing a quarter's product roadmap, deciding whether to kill a feature, or evaluating a product-market-fit claim without a supporting retention curve.
version: 1.0.0
category: Business & Ops / Executive Advisory
author: AgentVolt
license: proprietary
tags:
- business-ops
- executive-advisory
---
# Cpo Review
Runs a JTBD-driven interrogation of a product roadmap, PMF signal, and portfolio focus, the way a Chief Product Officer would before committing resources.
## When to use
… (sign up to view the full skill)More business & ops skills
View all Business & Ops skills →Gc Review
/cs:gc-review <plan> — General Counsel interrogation of contracts, IP, regulatory, term sheets, and employment-law surface.
Caio Review
/cs:caio-review <plan> — Eval-demanding Chief AI Officer interrogation of any plan that involves AI: model selection, risk classification, cost economics, or AI hiring.
Boardroom
/cs:boardroom <brief> — 6-phase multi-role deliberation across the C-suite with Phase 2 isolation, critic pre-screen, and synthesis.
Context Engine
Loads and manages company context for all C-suite advisor skills.