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.
Install
$ agentstack add skill-openplanr-openplanr-planr-cpo-review ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-openplanr-openplanr-planr-cpo-review) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →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
- Where does current evidence show users failing to reach value?
- 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.
- Is committed scope ordered by evidenced value and risk, or is the ordering not established?
- Which committed scope, if any, should be cut to protect the activation path?
- 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
- Source: openplanr/OpenPlanr
- License: MIT
- Homepage: https://openplanr.dev
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.