ccc-dashboard

Plugin ccc-dashboard from marketplace claude-command-center in amirfish1/claude-command-center. Commands read from the repo's manifest — today.

Skills (20)

• a-b-copy

  Use when you want a marketing-copy A/B — spawns two writer sibling sessions via CCC that draft the SAME message architecture in DIFFERENT voices, then a judge session (which saw neither draft happen) scores both and picks a winner.

• bug-race

  Use when a bug has already survived at least one debugging attempt and you have 2-3 genuinely distinct root-cause hypotheses — spawns one racer sibling session per hypothesis via CCC, referees the first CONFIRMED root cause with reproducible evidence, and stands the others down via inject.

• ccc-orchestration

  Spawn, inject into, and ask questions of persistent sibling sessions via Claude Command Center (CCC).

• docs-drift

  Use to catch documentation that has silently gone stale — it spawns ONE fresh sibling session via CCC that extracts every checkable factual claim from a doc (API fields, endpoint names, CLI flags, config keys, file paths, version numbers, example commands) and verifies each one against the actual co

• dogfood

  Use for docs QA — it spawns ONE fresh sibling session via CCC that has never seen the feature, has it follow the README / quickstart / docs cold in a scratch directory, and reports every stumble, ambiguity, and broken step as a doc bug. Fresh eyes are the whole point.

• fleet-lane-dispatch

  Use when dispatching a batch of autonomous CCC worker lanes with a mission brief and a report_to return address, or when receiving a lane assignment and needing to send a well-formed completion report — and, on the dispatcher side, before trusting a lane's SUCCEEDED report at face value.

• fleet-verify

  Use after a UI or user-visible change and before you claim it works — it spawns ONE CCC verification lane that drives a real browser (gstack browse, or CCC's puppeteer snapshot as fallback) against the running app, checks the specific thing you changed, and reports a visual/behavioral verdict with a

• group-chat-checkin

  Coordinate parallel sessions for discussion, task execution, and git commits.

• handoff

  Use to reset context without losing knowledge — it packages this session's state into a file, then spawns ONE fresh successor sibling session via CCC that verifies the package against the repo and takes over the mission. A clean baton pass onto the kanban, not lossy compaction.

• memory-recall

  Check CCC's cross-session memory before building a feature or acting on "earlier work" claims.

• pair-verify

  Use after you fix a bug and before you claim it fixed — it spawns ONE skeptic sibling session via CCC that must first reproduce the ORIGINAL bug on a clean worktree at the pre-fix ref, then prove your fix actually moves it. Reproduce-first discipline, independent of your context.

• press-room

  Use when one release needs to go out across several channels at once — spawns one writer sibling session per channel via CCC (changelog, LinkedIn, X thread, optional blog) off a single source pack, then collates the drafts.

• release-audit

  Use right before cutting a release — it spawns ONE fresh sibling session via CCC that audits only the JUDGMENT gates a release script cannot check (does the changelog actually describe the diff, does the version bump match semver for what changed, do the docs mention the new user-visible feature, is

• second-opinion

  Use when, before committing to a non-trivial approach, diagnosis, or answer, you want an independent check — it spawns ONE fresh sibling session via CCC (no shared context) to solve the same task from scratch, then diffs its answer against yours. Disagreement is the product.

• spawn-ux-worker

  Spawn a repo-scoped UX-fixes worker session that drains only one repo's UX-fixes queue, via the CCC API.

• standup

  Use when you want a one-line status from every live sibling session in a repo (or across repos) collated into a standup digest — queries siblings via CCC's `/api/ask` and spawns nothing.

• superpowers-to-watchtower

  Use when a superpowers plan (writing-plans / brainstorming output saved locally) is ready and you want durable, dashboard-visible tracking instead of an in-session scratch ledger — it imports the plan into a Watchtower queue as tickets, then optionally dispatches one CCC lane per ticket that closes

• threat-model

  Use before shipping a change that touches a trust boundary (a new endpoint, input parser, file-path handler, subprocess call, or auth check) — it spawns ONE fresh sibling session via CCC that maps the abuse surface of that specific diff, ranks each abuse case by impact and likelihood, and hands back

• vault

  Use when a task needs an API key, token, or login the user saved in CCC Settings > Vault. Run commands with the secret injected and redacted instead of reading the value.

• voice-guard

  Use to check ONE already-written piece of copy against a voice guide before it ships — it spawns ONE fresh sibling session via CCC that scores the existing draft against the stated voice rules, flags every violation with the offending quote and a minimal in-voice rewrite, and gives a ship / revise v

Similar plugins