Chief Product Officer Plan Review
A Chief Product Officer's verdict on one roadmap, PRD, or PMF claim: capacity math, evidence per item, metrics, and what changes the call.
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
Before you commit a quarter to a roadmap, get the review a demanding Chief Product Officer would give it. You get a verdict, the capacity math, and a clear call on every item.
What it does
- Traces every item to a segment, a job, and a metric with baseline and target
- Labels the evidence behind each item: usage data, repeated customer evidence, one big customer, or opinion
- Checks load against real capacity after maintenance and support work
- Tests product-market fit claims against cohort retention, by segment
- Makes keep-or-kill calls on features with usage, cost, and migration in view
What you get
A verdict (commit, commit with changes, rework), a capacity line, an item-by-item call table, ranked issues, conditions for commit, and what would change the verdict.
Best for
Heads of product, founders, and product leaders reviewing a roadmap, PRD, or product strategy before planning locks.
SKILL.md preview
---
name: cpo-review
description: Critique one product plan - a quarterly roadmap, a PRD, a product strategy doc, a product-market fit claim, or a keep-or-kill proposal for a feature - through a Chief Product Officer's lens and return a verdict (commit, commit with changes, rework), item-by-item calls, the capacity math, the evidence gaps, and what would change the verdict. Use when the user says "review our roadmap before we commit", "would a CPO sign off on this?", "poke holes in this PRD", "we're claiming PMF, is that fair?", "should we kill this feature?", "is this roadmap realistic?", or pastes a roadmap and asks "what's wrong with it?".
---
# Chief Product Officer Plan Review
… (sign up to view the full skill)More business & ops skills
View all Business & Ops skills →Simulated Board Pressure Test
Stress-tests a proposal from each board seat's incentives, forecasts the vote, and names the changes that would get it approved.
New Executive Onboarding Plan
First 90 days for a new VP or C-level hire: decision rights from the founder, a measurable scorecard, listening tour, 30/60/90 check-ins.
Change Rollout Planner
Plans how one reorg, tool switch, or pivot lands: impact by group, who hears what first, resistance diagnosis, and follow-through.
CEO Board Prep and Pre-Wires
Gets a CEO ready for the board: likely hard questions by director, number-first answers, pre-wire calls, and a vote count.