cpo

Prioritizes product roadmaps and feature scope using RICE scoring and strategic fit frameworks.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/beelabstudio/ai --skill cpo-beelabstudio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cpo
Source: https://github.com/beelabstudio/ai/tree/main/skills/c-level/cpo
Command: npx skills add https://github.com/beelabstudio/ai --skill cpo-beelabstudio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product teams struggle to decide which features to build, defer, or reject when facing competing requests from sales, support, and engineering. This Skill applies a Chief Product Officer perspective to make roadmap sequencing, scope, and prioritisation decisions with structured frameworks instead of gut feel. ## Core Features & Use Cases - Roadmap Prioritisation: Scores every roadmap item with RICE (Reach, Impact, Confidence, Effort) plus a strategic-fit override so high-scoring items that conflict with the product vision are still deferred. - Scope Governance: Applies the Jobs-to-be-Done gate, a scope reduction protocol for overloaded sprints, and distinct MVP vs. production quality thresholds. - Structured Decision Output: Produces a consistent decision record covering problem statement, affected personas, horizon, options compared, scope in/out, acceptance criteria, and success metrics. - Use Case: When sales demands a new reporting module mid-sprint, use this Skill to evaluate the request against the North Star metric, compare it with existing roadmap items, and produce a documented approve/defer/reject decision. ## Quick Start Act as the CPO and decide whether the proposed feature request should enter the backlog, the active sprint, or be rejected, using the RICE and strategic fit frameworks.

Frequently Asked Questions about cpo

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prioritize a product roadmap with RICE?▼

Score each roadmap item on Reach, Impact, Confidence, and Effort, then apply a strategic fit override. A high-RICE feature that conflicts with the product vision is still deferred, since RICE scores inform decisions rather than make them.

How to decide if a feature request belongs in the sprint or backlog?▼

Run the request through the Jobs-to-be-Done gate: identify what job the user hires the feature to do and whether you want to be best in the world at it. If the answer is no or uncertain, the feature goes to the icebox.

What is the difference between MVP and production quality thresholds?▼

MVP threshold requires solving the core user pain safely and correctly before shipping. Production threshold additionally requires the feature to be delightful, performant, and scalable, which is addressed in a V1 polish sprint.

How do I handle an overloaded sprint without cutting scope silently?▼

Identify the 20 percent of scope delivering 80 percent of the value, move the remainder to a documented V2 of the story, and record exactly what was cut and why. Acceptance criteria must never be reduced without documentation.

When should I use a domain-specific product-owner skill instead?▼

If the project has its own product-owner skill scoped to a particular vertical or user base, check its AGENTS.md first and prefer it for product-specific decisions. Use the generic CPO skill for cross-cutting strategy and prioritisation.