ccc-broadcastlisted

# $ccc-broadcast — Outbound Status Relay > Placeholders like `~~chat` and `~~email` refer to connected tools. See [CONNECTORS.md](../../CONNECTORS.md). Turn "did the deploy work?", "is the site up?", and "did the overnight run finish?" into pushed status updates. `ccc-broadcast` watches the operational signals a CC Commander session already produces — builds, deploys, CI results, task completions, cost/budget alerts — and relays a plain-language summary to the channels a team actually reads (`~~chat`, `~~email`). No dashboards to open, no terminal to babysit. This is the **outbound-status counterpart to `$ccc-nightwatch`** (which relays *approval requests* to your phone). Nightwatch asks "can I do this?"; broadcast tells "here's what happened." ## What it does The skill maps CC Commander lifecycle events to a small set of business-legible messages and forwards them through whatever `~~chat` or `~~email` connector is enabled via `$ccc-connect`. Each relay is a short, scrubbed summary — event type, human outcome, and a link if one exists — never file contents, diffs, or secret values. Signals are classified by audience so engineers, owners, and clients each get the right altitude. ## Triggers - `$ccc-broadcast` - "tell the team when the deploy finishes" - "send me a status when the build is done" - "broadcast ops updates to Slack" - "let the client know when it's live" - "team status updates" ## Signal → Audience Matrix | Signal | Example | Default audience | Channel |