Plan and operate a product, feature, beta, early-access, or general-availability launch from readiness gate through post-launch adoption: launch brief, phase design, channel roles and asset map, launch-platform preparation, a timed run-of-show with owners and stop conditions, health monitoring, and correction. Use when preparing a public release; use press-kit for earned media and third-party-listings for store and directory presence.
Installs into .claude/skills of the current project.
Are you the author of Launch Runbook?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/mtent-launch-runbook)
---
name: launch-runbook
description: Plan and operate a product, feature, beta, early-access, or general-availability launch from readiness gate through post-launch adoption: launch brief, phase design, channel roles and asset map, launch-platform preparation, a timed run-of-show with owners and stop conditions, health monitoring, and correction. Use when preparing a public release; use press-kit for earned media and third-party-listings for store and directory presence.
license: MIT
metadata:
version: "2.0.0"
author: MTEnt
---
# Launch Runbook
Separate shipping, announcing, and broad availability. Attention does not repair an unready product or support path.
If `.agents/marketing-context.md` exists, read it first; it is the truth file every skill in this hub shares, and its evidence states are constraints. Read [launch-system.md](references/launch-system.md) for the readiness gate, launch brief, phases, channel roles, launch platforms, launch-day operations, and post-launch work.
## Operating contract
1. Verify what is shipping, for whom, where, when, at what price, with which limits, migration, support, security or privacy changes, and approved proof.
2. Choose the launch's primary job: learning, activation, demand, sales enablement, migration, category story, or broad availability.
3. Use phases only when they control risk or improve learning; give each channel one job and keep availability, terms, claims, and destination consistent.
4. Define readiness, owners, support, monitoring, correction, pause, and post-launch adoption before publication.
5. Require authorization before outreach, scheduling, publication, launch-platform activity, or spend.
Do not fabricate availability, customers, quotes, partnerships, votes, reviews, urgency, or launch success.
## Return
Launch decision, readiness matrix, phase plan, audience and message, channel and asset map, timeline and owners, rights and approvals, run-of-show, measurement, incident and correction plan, and post-launch adoption work.
