cocoops

Objective

You are the CocoOps dispatch router. Route $ops sub-commands to the appropriate CocoOps sub-skills.

Before proceeding, verify that .cocoplus/ exists. If not, output: "CocoPlus is not initialized. Run $pod init first." Then stop.

Routing Table

Command	Sub-skill	Description
$ops dora	.cortex/skills/cocoops/ops-dora/SKILL.md	DORA-adapted delivery metrics
$ops sprint	.cortex/skills/cocoops/ops-sprint/SKILL.md	Current sprint health
$ops suggest	.cortex/skills/cocoops/ops-suggest/SKILL.md	Time-aware operational suggestions
$ops demo	.cortex/skills/cocoops/ops-demo/SKILL.md	Activate demo mode
$ops refresh	.cortex/skills/cocoops/ops-dora/SKILL.md	Re-run DORA computation and update snapshot
$ops (no args)	Show dashboard summary	Display last dora-snapshot.json summary with color-coded metric cards in text form
$ops dashboard	Show dashboard summary	Alias for $ops default dashboard

Default View (no args)

If invoked with no sub-command, display a brief status dashboard:

CocoOps — <project> — <date>

Last DORA snapshot: <timestamp or "None — run $ops dora">
Overall health: <tier or "Unknown">

Metric cards:
  Pipeline Run Frequency    [GREEN/YELLOW/RED] <value> <tier>
  Data Availability Lead    [GREEN/YELLOW/RED] <value> <tier>
  Failure Recovery Time     [GREEN/YELLOW/RED] <value> <tier>
  Quality Failure Rate      [GREEN/YELLOW/RED] <value> <tier>

Trend bands:
  Use dora-thesis.md when present to summarize improving / flat / worsening longitudinal direction.

Quick commands:
  $ops dora     — Compute full DORA metrics
  $ops sprint   — Current sprint health
  $ops suggest  — What to focus on now
  $ops demo     — Activate demo mode

Read .cocoplus/ops/dora-snapshot.json for the summary data. If absent, suggest running $ops dora.

Exit Criteria

• All sub-commands route to correct sub-skills
• Default view shows last snapshot summary
• Unknown sub-commands show routing table with available options

Anti-Rationalization

Shortcut / Temptation	Why It Fails
Treat the skill as complete because the file exists	Skill contracts must describe observable behavior and verification, not just command names.
Skip artifact and safety checks for a small command	Small commands still mutate state or guide execution; preserve the same gates.