cpo

Frame strategic product bets into three paths with kill criteria.

6|1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/0x2kNJ/cpo --skill cpo-0x2knj
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cpo
Source: https://github.com/0x2kNJ/cpo/tree/main
Command: npx skills add https://github.com/0x2kNJ/cpo --skill cpo-0x2knj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured decision layer to help founders and product teams decide what to build, whether to build it, and when to kill a bet before committing resources.

Core Features & Use Cases

  • Structured decision framing: Gates ([FRAME], [PATHS], [VERDICT]) ensure disciplined framing and traceability.
  • Three-path decision framework: Proposes three distinct options with explicit trade-offs and kill criteria.
  • Journal and signals integration: Logs decisions locally and surfaces signals to downstream skills for alignment.
  • Mode-driven workflows: Supports --go, --deep, --quick, --save-context, and --decide for flexible usage across stages.

Quick Start

Prompt CPO with a decision prompt and let it generate a FRAME + PATHS flow and three kill criteria.

Frequently Asked Questions about cpo

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

FAQPage Schema
How do I make structured product decisions on what to build?▼

Structured product decisions require framing strategic bets and surfacing viable paths with explicit kill criteria before committing resources. This approach generates three distinct options with clear trade-offs and a recommended verdict to ensure disciplined framing and traceability.

What is a three-path decision framework for product management?▼

A three-path decision framework proposes three distinct product options, each with explicit trade-offs and kill criteria. It gates decisions through a structured flow that outputs a recommended option and a closing verdict to support strategic product bets.

How do I define kill criteria for a product bet?▼

Kill criteria for a product bet are defined by framing strategic options and explicitly setting thresholds for when to abandon a path. This structured gating surfaces three viable paths, each with tailored kill criteria to prevent overcommitting resources.

Can I log product decisions locally and surface signals to downstream skills?▼

Logging product decisions locally and surfacing signals to downstream skills is supported through journal integration. Decisions are written to a local journal during the gating flow, ensuring alignment and traceability for future product management actions.

What is the best way to run quick versus deep product decision workflows?▼

Quick versus deep product decision workflows are managed through mode-driven flags like --quick and --deep. These modes adjust the depth of the structured gating flow, allowing teams to flexibly frame decisions and generate paths across different stages.

When should I use a structured gating flow for product decisions?▼

A structured gating flow for product decisions should be used when deciding what to build, whether to build it, and when to kill a bet before committing resources. It ensures disciplined framing, generates three viable paths, and records a final verdict.