Agent skill · operations · borghei
launch-playbook
Internal and external launch coordination playbook covering pre-launch, launch day, and post-launch with run-of-show, comms, RACI, rollback, and retro. Use to coordinate a GA launch, major release, or re-launch.
Why this skill is useful
Provides a structured framework for coordinating complex software launches, ensuring all stakeholders are aligned and accountable, which the AI wouldn't reliably generate on its own.
What it needs
About 4k tokens when loaded. Last updated 2026-07-21. 462 stars on the source repository.
What this skill does
Launch Playbook (Internal + External Coordination) Overview A complete launch coordination playbook for software products and features. It covers the three windows that matter -- pre-launch (T-30 to T-1), launch day (T-0), and post-launch (T+1 to T+30) -- and produces five concrete artifacts: a run-of-show, an internal comms plan, an external comms checklist, a rollback plan, and a post-launch retro template. Most failed launches are not failed builds; they are failed coordination. Engineering ships on time, but support has not been trained, sales does not have collateral, the changelog is wrong, the rollback path was never tested, and the executive sponsor hears about a customer complaint before hearing about the launch. This playbook prevents those failures by assigning every owner and every artifact before T-30. Core Capabilities Three-launches sequencing — Cagan's alpha/beta/GA model de-risks the launch; this skill owns the GA window. T-30 to T+30 timeline — day-by-day pre-launch, launch-day, and post-launch action plan across all workstreams. Launch-type selection — big bang vs progressive rollout vs dark launch decision rules (and how to combine them). RACI ownership — every workstream assigned across PM, Eng, PMM, Sales, Support, Legal, Exec. Five artifacts — run-of-show, internal comms plan, external comms checklist, rollback plan, post-launch retro. When to Use GA after closed beta -- A feature is exiting beta (see beta-program/) and needs coordinated launch. Major version release -- Significant new functionality with cross-functional dependencies (sales enablement, support training, legal review). Re-launch / repositioning -- An existing feature is being relaunched with new positioning, pricing, or audience. High-blast-radius change -- Infrastructure migration, pricing change, or breaking API change requiring tightly coordinated comms. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills borghei/launch-playbook