Skip to content
Back to skills

Planr Coo Review

ASecurity

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.

  • 5 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 23, 2026
developmentgo

Security analysis

A100/100

Pro scans all 11 files and shows the line behind each finding

Scanned October 7, 2026

npx -y skills add openplanr/OpenPlanr --skill planr-coo-review --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Planr Coo Review?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Planr Coo Review
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/openplanr-planr-coo-review/badge)](https://www.skillsdirectory.com/skills/openplanr-planr-coo-review)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: planr-coo-review
description: "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."
license: MIT
---

# OpenPlanr COO Review

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

## Return

Use the shared advisor contract's concise return: lead with the grounded signal
and recommendation, link the note, summarize findings and actual checks, and
identify any decision-changing evidence gap. Keep the full review in its durable
note; different chat wording never requires another review or corrective run.

Files in this skill

  • SKILL.md1.9 KB
  • agents/openai.yaml387 B
  • compatibility.json324 B
  • host-profiles.json5.6 KB
  • modules.json1.1 KB
  • openplanr.skill.json1.3 KB
  • references/operate-advisor-contract.md4.5 KB
  • scripts/errors.mjs205 B
  • scripts/operate-review-contract.mjs12.1 KB
  • scripts/operate-review-note.mjs22.4 KB
  • scripts/validate-note.mjs1.1 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.