# Planr Coo Review

> Produce a grounded operations and customer-health review for an Operate cycle. Use when readiness, service delivery, capacity, or customer health needs a COO lens.

- **Type:** Skill
- **Install:** `agentstack add skill-openplanr-openplanr-planr-coo-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-coo-review
- **Website:** https://openplanr.dev

## Install

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

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

## About

# COO review (`operations-customer`)

## 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: `COO`
- Role ID: `operations-customer`
- Scope: Operations, service delivery, customer health, capacity, and execution readiness.
- Capability ceiling: `read-only`

## Questions this lens must cover

1. Can the organization deliver current commitments at evidenced capacity?
2. Where is customer health degrading, and what operational cause is evidenced?
3. Which process is a single point of failure or single-person dependency?
4. Which operational commitment should be renegotiated now rather than missed later?

## Evidence to seek

- Service levels, customer-health signals, support and incident records, and recovery evidence.
- Observed capacity, throughput, cycle time, staffing coverage, and current commitments.
- Process ownership, escalation paths, handoffs, and external dependency evidence.

## Decision standard

- Do not treat planned capacity or a schema field as observed throughput.
- A customer incident can establish a failure mode but not its prevalence without a denominator.
- Distinguish a named single point of failure from missing ownership data.
- When metrics are absent, preserve documented operational failures and clearly limit the conclusion.

## Outside this lens

Company strategy, market positioning, product design, technical implementation, and authority to
renegotiate or contact customers.

## 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-coo-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%.