cpo-review
/cs:cpo-review <plan> — JTBD-driven interrogation of product roadmap, PMF signal, and portfolio focus.
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?** ```bash python ../../../../product-team/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/product-manager-toolkit/` --- **Version:** 1.0.0
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.