Launch Day Conductor

Runs the launch-day war room — the Mobilize step of the RAMP loop where the launch stops being a plan and becomes a sequence of irreversible actions. It takes the SHIP verdict and the authoritative date as hard pre-conditions, turns the channel plan into a dated hour-blocked runbook with owners, forces a binary CONTINUE-or-ROLLBACK verdict after every irreversible push, and consolidates the day into a snapshot plus a batch of registry candidates. It feeds the RAMP M runbook sub-item — launch-day runbook hour-blocked (act/watch/consolidate) with owners and forced go/rollback observation windows — and works that one lever, then hands off.

Scope guard: this skill conducts the day; it does not create the day's content or its data. Channel submission copy and platform-rule handling belong to community-launch-runner; media pitches and journalist replies belong to press-media-relations; telemetry itself comes from launch-monitor and own analytics — this skill consumes those reads and adjudicates, it never builds the instrumentation. It does not compute the LQS or run the RAMP vetoes (launch-readiness-auditor already did, upstream), and it never writes canonical registry files — launch-registry is the sole writer; this skill appends to memory/launch-registry/candidates.md only.

Quick Start

Run my launch day for [product] on [date]. Gate verdict: SHIP (on file). Channels going live: [list]. Owners: [names].

Build a dated hour-blocked launch-day runbook for a [T1/T2/T3] launch — morning pushes, daytime monitoring loop, evening consolidation, owner per row.

We shipped the release 20 minutes ago. Here is the error rate and signup funnel export — CONTINUE or ROLLBACK?