| name | launch-day-conductor |
| slug | aaron-launch-day-conductor |
| displayName | Launch Day Conductor · 发布日指挥 |
| summary | 发布日runbook/作战室/观察窗/回滚裁决 |
| description | Use when the user asks to "run my launch day", "build a launch day runbook / war room", or "decide CONTINUE or ROLLBACK after the push"; produces a pre-conditions gate check (launch-readiness-auditor SHIP verdict + the authoritative date in launch-registry — missing either stops the skill), a dated hour-blocked runbook with owners (morning irreversible pushes, daytime monitoring loop, evening consolidation), a forced observation-window verdict after every irreversible action against pre-declared kill criteria, a P0-P3 incident ladder with rollback playbooks, and T-0 status lines for the registry proposal protocol. Not for channel submission content and platform rules — use community-launch-runner; not for media replies — use press-media-relations. 发布日runbook/作战室/观察窗/回滚裁决/发布日指挥 |
| version | 19.2.0 |
| license | Apache-2.0 |
| compatibility | Claude Code and compatible agent-skill hosts |
| homepage | https://github.com/aaron-he-zhu/aaron-marketing-skills |
| when_to_use | Use when conducting the launch day itself: verifying the two pre-conditions (SHIP verdict from launch-readiness-auditor + the authoritative date/stage in launch-registry), generating the dated hour-blocked runbook with an owner column, forcing a CONTINUE-or-ROLLBACK verdict after each irreversible push, classifying incidents P0-P3 and running rollback playbooks, or consolidating the day into a snapshot plus registry proposals. The war-room layer between the T-1 gate and the T-0 to T+30 monitoring window. |
| argument-hint | <product / launch date> [tier] [channel plan + owners] [kill criteria source] |
| metadata | {"author":"aaron-he-zhu","version":"19.2.0","discipline":"launch","phase":"mobilize","geo-relevance":"low","hermes":{"tags":["marketing","launch","mobilize"],"category":"launch"},"openclaw":{"emoji":"🚀","homepage":"https://github.com/aaron-he-zhu/aaron-marketing-skills"}} |
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 proposals. 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 RAMP profile result 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 submits proposal events to memory/events/launches.ndjson via an authorized operation: propose request to registry-events.py 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?
Skill Contract
Expected output: a pre-conditions verification (pass, or NEEDS_INPUT with the missing record named), a dated hour-blocked runbook with an owner column, an observation-window + binary-verdict schedule for every irreversible action, a P0-P3 incident ladder with rollback playbooks, an end-of-day consolidation (D0 snapshot, thank-you queue, next-day queue, registry proposals batch), and the standard handoff summary.
