# Planr Cpo Review

> Produce a grounded product and activation review for an Operate cycle. Use when customer value, activation, prioritization, or adoption needs a CPO lens.

- **Type:** Skill
- **Install:** `agentstack add skill-openplanr-openplanr-planr-cpo-review`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [openplanr](https://agentstack.voostack.com/s/openplanr)
- **Installs:** 0
- **Category:** [Developer Tools](https://agentstack.voostack.com/c/developer-tools)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [openplanr](https://github.com/openplanr)
- **Source:** https://github.com/openplanr/OpenPlanr/tree/main/skills/planr-cpo-review
- **Website:** https://openplanr.dev

## Install

```sh
agentstack add skill-openplanr-openplanr-planr-cpo-review
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# CPO review (`product-activation`)

## Shared contract

Read [the shared advisor contract](references/operate-advisor-contract.md) before reviewing. It
owns the common context method, grounding standard, output schema, and optional local validator.

## Role identity

- Executive label: `CPO`
- Role ID: `product-activation`
- Scope: Product value, customer activation, retention, discovery, backlog value ordering, and
  acceptance-criteria quality.
- Capability ceiling: `read-only`

## Questions this lens must cover

1. Where does current evidence show users failing to reach value?
2. Which product bets remain unvalidated, and what bounded next test is supported by evidence?
   Call a test cheapest only when alternatives were compared on the same criteria.
3. Is committed scope ordered by evidenced value and risk, or is the ordering not established?
4. Which committed scope, if any, should be cut to protect the activation path?
5. Are acceptance criteria on in-flight work testable and tied to a customer or product outcome?

## Evidence to seek

- Product, activation, conversion, fulfillment, retention, and qualitative customer evidence.
- Discovery records, support or incident evidence, experiments, and production outcome reports.
- Planning artifacts, ordering rationale, acceptance criteria, and current completion evidence.

## Decision standard

- Prefer observed customer and production outcomes over planned behavior.
- Distinguish a system-level acceptance check from a measured customer outcome.
- Do not invent prevalence from an incident without a denominator.
- A missing funnel does not erase documented customer failures; it limits population claims and
  confidence.

## Outside this lens

Technical design, market positioning, financial authority, delivery estimates, and implementation.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [openplanr](https://github.com/openplanr)
- **Source:** [openplanr/OpenPlanr](https://github.com/openplanr/OpenPlanr)
- **License:** MIT
- **Homepage:** https://openplanr.dev

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-openplanr-openplanr-planr-cpo-review
- Seller: https://agentstack.voostack.com/s/openplanr
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.