cc-operator

Plugin cc-operator from marketplace betmoar in betmoar/ccp-market. Commands read from the repo's manifest — 1 month ago.

Skills (2)

• chief-operator

  Use when the user asks to run as chief operator, orchestrate this, operator mode, or set up an engagement — routing to the operator charter and its start command.

• holdout

  Use when deriving, repairing or re-deriving a holdout — a check suite written from the spec by something that cannot read the code — or when a holdout check disagrees with the system, or when tempted to hand-edit one.

Slash commands (11)

• /cc-operator:brainstorm

  Run the brainstorm workflow — N divergent directions, a blindspot scan of this codebase, and a reference search, converged into ranked options and the questions only you can answer.

• /cc-operator:crawl

  Run the crawl workflow — one cheap crawler seat per shard in parallel, then a judgment-tier merge — to digest a large corpus without paying judgment tier for the reading.

• /cc-operator:debate

  Run the debate workflow — 2-5 named models argue the same case over three blind rounds, then a neutral synthesis. It never picks a winner; you decide.

• /cc-operator:handoff

  Run when ending an operated engagement or session — to produce the structured operator→human handoff before you stop or hand off.

• /cc-operator:implement

  Run the implement workflow — one implementer seat per task, serially, on the IMPLEMENT tier, refusing an incomplete dispatch packet before spending a seat.

• /cc-operator:plan

  Run the plan workflow — decompose an approved spec into TDD tasks, then vet each in parallel for feasibility and testability.

• /cc-operator:review

  Run the review workflow over an artifact — parallel narrow lenses then an adversarial verifier — with the tier bindings resolved for you.

• /cc-operator:spec

  Write, check and approve the engagement's spec — the artifact that carries an approved design from brainstorm into plan, with a source stamp and a ledger row.

• /cc-operator:start

  Run at the start of a session you will operate as chief operator — orchestrating an engagement, gating on evidence, or driving multi-step work to a verified done-state.

• /cc-operator:tiers

  Resolve tier→model bindings, apply one-off overrides, or render project-layer agents so plain Agent dispatch can run on a configured cc-proxy model. Wraps the resolver (ops-tiers.sh) and renderer (ops-render.sh) — the command adds no logic; those scripts' charset guard is the validation.

• /cc-operator:tutorial

  Watch the evidence gate work — a throwaway project where the real Stop hook blocks on an open task and then lets the stop through once a verdict row records the evidence.

Subagents (8)

• op-author

  Judgment-tier implementer for prose, design, and any work whose quality depends on taste or reasoning, dispatched by the operator.

• op-brainstorm

  Divergent idea generator — many genuinely distinct candidate approaches, names, or angles. Generation, not judgment; a stronger model evaluates and chooses. Dispatched by the operator or the brainstorm workflow.

• op-crawler

  One-shard code crawler for large-corpus fan-outs — reads the assigned shard (explicit paths) and returns a dense, faithful digest. Read-only. Does NOT fan out; the crawl workflow owns sharding and merging. Dispatched by the crawl workflow or the operator.

• op-debater

  Read-only debate seat — holds ONE position across rounds, engages rival positions on their strongest form, and revises only on evidence. Dispatched by the debate workflow.

• op-mechanic

  Mechanical-tier implementer for scaffolds, verbatim-specified files, fixtures, verification commands, commits, and reverts, dispatched by the operator.

• op-reviewer

  Judgment-tier read-only reviewer and scorer, dispatched by the operator. Runs in spec mode, quality mode, or scoring mode as set per dispatch.

• op-scout

  Recon-tier read-only scout for searches, lookups, and "where/how is X" questions that need no judgment, dispatched by the operator.

• op-verifier

  Fresh-context adversarial verifier, dispatched by the operator after implementation work — independently tries to refute the claimed outcome and returns CONFIRMED or REFUTED with evidence.

Hooks (3)

• SessionStart

  bash "${CLAUDE_PLUGIN_ROOT}/scripts/ops-sessionstart-hook.sh"

• Stop

  bash "${CLAUDE_PLUGIN_ROOT}/scripts/ops-stop-hook.sh"

• PostToolUse

  command -v node >/dev/null 2>&1 || exit 0; node "${CLAUDE_PLUGIN_ROOT}/scripts/ops-compress.mjs"

Similar plugins