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.