Menu

Individual skill

launch-day-conductor

0upvotes

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/作战室/观察窗/回滚裁决/发布日指挥

launch/mobilize/launch-day-conductor/SKILL.md

Read pinned source

Source commit 8be02f1f0b18253bd5f2b85f858278f042637b9a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
3,137
Repository last updated
Nov 12, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Declared tags are partial or unavailable.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Launch Day Conductor

Runs the launch-day war room — the Mobilize step of the [RAMP loop](../../../references/ramp-benchmark.md) 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](../community-launch-runner/SKILL.md); media pitches and journalist replies belong to [press-media-relations](../press-media-relations/SKILL.md); telemetry itself comes from [launch-monitor](../../prove/launch-monitor/SKILL.md) 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](../launch-readiness-auditor/SKILL.md) already did, upstream), and it never writes canonical registry files — [launch-registry](../../../protocol/launch-registry/SKILL.md) 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.
Back to top