launch-runbook
Plan and execute a launch runbook covering pre-launch verification, go-live procedures, DNS cutover, post-launch monitoring, and rollback procedures. Use this skill whenever the user is preparing to launch a website or product, planning a DNS cutover, building a go-live checklist, or executing a launch day. Triggers on launch runbook, go-live, launch day, DNS cutover, deploy to production, site launch, product launch, cutover plan, launch checklist, deployment procedure. Also triggers when a launch is approaching and the team needs structured coordination, even if 'runbook' is not explicitly s
Profile →npx skills add rampstackco/claude-skills --skill launch-runbook --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Launch Runbook Plan and execute the launch of a website, product, or major release. The runbook is the document everyone uses on launch day. Stack-agnostic. This skill is for the launch event. For pre-launch QA, use `qa-testing`. For post-launch incident handling, use `incident-response`. --- ## When to use - Launching a new website or major redesign - Migrating from one platform to another - Releasing a major product or feature - Coordinating cross-team launches - Building a runbook for a recurring deploy ## When NOT to use - Pre-launch testing (use `qa-testing`) - Post-launch incident response (use `incident-response`) - After-launch retrospective (use `after-action-report`) --- ## Required inputs - The launch scope (what's being launched) - The launch window (date, time, duration) - The team (roles, on-call rotation) - The rollback criteria (when to abort) - The communication plan (who tells whom what, when) --- ## The framework: 4 phases A launch has four phases. The runbook covers all four. ### Phase 1: Pre-launch (T-30 days to T-1 hour) Verify everything is ready before the launch window. **T-30 days:** - Final scope locked - Cross-team commitments confirmed - Pre-launch QA
- When to use
- When NOT to use
- Required inputs
- The framework: 4 phases
- Phase 1: Pre-launch (T-30 days to T-1 hour)
- Phase 2: Cutover (T-0)
- Phase 3: Verification (T+0 to T+24 hours)
- Phase 4: Stabilization (T+24 hours to T+7 days)
- Roles and responsibilities
- Rollback criteria
- Communication plan
- Internal channels
- Update cadence during launch
- External communication
What does the launch-runbook skill do?
Plan and execute a launch runbook covering pre-launch verification, go-live procedures, DNS cutover, post-launch monitoring, and rollback procedures. Use this skill whenever the user is preparing to launch a website or product, planning a DNS cutover, building a go-live checklist, or executing a launch day. Triggers on launch runbook, go-live, launch day, DNS cutover, deploy to production, site launch, product launch, cutover plan, launch checklist, deployment procedure. Also triggers when a launch is approaching and the team needs structured coordination, even if 'runbook' is not explicitly s
How do I install it?
Run `npx skills add rampstackco/claude-skills --skill launch-runbook --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From rampstackco/claude-skills, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.