cpo-review
$
npx mdskill add alirezarezvani/claude-skills/cpo-review**Command:** `/cs:cpo-review <plan>`
SKILL.md
.github/skills/cpo-reviewView on GitHub ↗
--- 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?" ## 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?** ```bash 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:** ```bash python ../../../skills/cpo-advisor/scripts/pmf_scorer.py python ../../../skills/cpo-advisor/scripts/portfolio_analyzer.py ``` 2. **Answer the six questions.** 3. **Apply the verdict.** ## Output Format ```markdown # 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`](../../agents/cs-cpo-advisor.md) - Skill: [`cpo-advisor`](../../../skills/cpo-advisor/SKILL.md) - Execution: `product-team/skills/product-manager-toolkit/` --- **Version:** 1.0.0
More from alirezarezvani/claude-skills
- a11y-auditAccessibility audit skill for scanning, fixing, and verifying WCAG 2.2 Level A and AA compliance across React, Next.js, Vue, Angular, Svelte, and plain HTML codebases. Use when auditing accessibility, fixing a11y violations, checking color contrast, generating compliance reports, or integrating accessibility checks into CI/CD pipelines.
- ab-test-setupWhen the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "conversion experiment," "statistical significance," or "test this." For tracking implementation, see analytics-tracking.
- ad-creativeWhen the user needs to generate, iterate, or scale ad creative for paid advertising. Use when they say 'write ad copy,' 'generate headlines,' 'create ad variations,' 'bulk creative,' 'iterate on ads,' 'ad copy validation,' 'RSA headlines,' 'Meta ad copy,' 'LinkedIn ad,' or 'creative testing.' This is pure creative production — distinct from paid-ads (campaign strategy). Use ad-creative when you need the copy, not the campaign plan.
- adversarial-reviewerAdversarial code review that breaks the self-review monoculture. Use when you want a genuinely critical review of recent changes, before merging a PR, or when you suspect Claude is being too agreeable about code quality. Forces perspective shifts through hostile reviewer personas that catch blind spots the author's mental model shares with the reviewer.
- aeoAnswer Engine Optimization (AEO) skill — optimize content to be cited by AI language models (ChatGPT, Perplexity, Claude, Gemini, Mistral) as authoritative sources. Distinct from SEO — AEO optimizes for citation in LLM-generated responses, not search rankings. Use when planning content for AI-first search audiences, auditing existing content for E-E-A-T signals, tracking which pages get cited by which LLMs, or building a citation-friendly content strategy. Triggers — 'AEO audit', 'optimize for ChatGPT', 'get cited by Perplexity', 'LLM citation strategy', 'answer engine optimization', 'content for AI search', 'E-E-A-T audit'. Output is a markdown audit report (default) or JSON for pipeline integration. Stdlib-only Python tools.
- agent-designerUse when the user asks to design a multi-agent system, pick an orchestration pattern (supervisor/swarm/pipeline), generate tool schemas for agents, or evaluate agent execution logs for cost, latency, and failure bottlenecks. Examples: 'design an agent architecture for research automation', 'generate Anthropic tool schemas from these tool descriptions', 'analyze these agent run logs for bottlenecks'. NOT for Claude Code workflow files (use workflow-builder) or single-agent prompt design (use agent-workflow-designer).
- agent-protocolInter-agent communication protocol for C-suite agent teams. Defines invocation syntax, loop prevention, isolation rules, and response formats. Use when C-suite agents need to query each other, coordinate cross-functional analysis, or run board meetings with multiple agent roles.
- agent-workflow-designerDesign production-grade multi-agent workflows with clear pattern choice (sequential, parallel, hierarchical), handoff contracts, failure handling, and cost/context controls. Use when architecting a multi-step agent pipeline, choosing between single-agent vs multi-agent approaches, or refactoring an LLM workflow that suffers from context bloat or unreliable handoffs.
- agenthubMulti-agent collaboration plugin that spawns N parallel subagents competing on the same task via git worktree isolation. Agents work independently, results are evaluated by metric or LLM judge, and the best branch is merged. Use when: user wants multiple approaches tried in parallel — code optimization, content variation, research exploration, or any task that benefits from parallel competition. Requires: a git repo.
- agile-product-ownerAgile product ownership for backlog management and sprint execution. Covers user story writing, acceptance criteria, sprint planning, and velocity tracking. Use when writing user stories, creating acceptance criteria, planning sprints, estimating story points, breaking down epics, or prioritizing the backlog.