Release Engineering
majiayu000/spellbook
Plan and verify software releases with versioning, changelogs, release branches, feature flags, canaries, migration gates, rollback, deployment checks, and release readiness.
Internal and external launch coordination playbook covering pre-launch, launch day, and post-launch with run-of-show, comms, RACI, rollback, and retro.
Install Launch Playbook
$ npx skills add borghei/Claude-Skills --skill launch-playbook -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install borghei/Claude-Skills launch-playbook --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/project-management/execution/launch-playbook .claude/skills/launch-playbook && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "launch-playbook" agent skill from https://github.com/borghei/Claude-Skills/tree/main/project-management/execution/launch-playbook into .claude/skills/launch-playbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-playbook", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/borghei/Claude-Skills/tree/main/project-management/execution/launch-playbookType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add borghei/Claude-Skills --skill launch-playbook -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install borghei/Claude-Skills launch-playbook --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/project-management/execution/launch-playbook .agents/skills/launch-playbook && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "launch-playbook" agent skill from https://github.com/borghei/Claude-Skills/tree/main/project-management/execution/launch-playbook into .agents/skills/launch-playbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-playbook", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill launch-playbook -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install borghei/Claude-Skills launch-playbook --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/project-management/execution/launch-playbook .cursor/skills/launch-playbook && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "launch-playbook" agent skill from https://github.com/borghei/Claude-Skills/tree/main/project-management/execution/launch-playbook into .cursor/skills/launch-playbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-playbook", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/borghei/Claude-Skills.git --path project-management/execution/launch-playbook--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add borghei/Claude-Skills --skill launch-playbook -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install borghei/Claude-Skills launch-playbook --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/project-management/execution/launch-playbook .gemini/skills/launch-playbook && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "launch-playbook" agent skill from https://github.com/borghei/Claude-Skills/tree/main/project-management/execution/launch-playbook into .gemini/skills/launch-playbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-playbook", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install borghei/Claude-Skills launch-playbookInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add borghei/Claude-Skills --skill launch-playbook -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/project-management/execution/launch-playbook .github/skills/launch-playbook && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "launch-playbook" agent skill from https://github.com/borghei/Claude-Skills/tree/main/project-management/execution/launch-playbook into .github/skills/launch-playbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-playbook", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill launch-playbook -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install borghei/Claude-Skills launch-playbook --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/project-management/execution/launch-playbook .opencode/skills/launch-playbook && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "launch-playbook" agent skill from https://github.com/borghei/Claude-Skills/tree/main/project-management/execution/launch-playbook into .opencode/skills/launch-playbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-playbook", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
launch-playbook- GitHub stars
- 881
- Token cost
- ~1.8k tokens
- SKILL.md length
- 825 words
- Files
- 10 (incl. references, assets)
- Skills in repo
- 349
- Repo updated
- First seen
- Licence
- MIT
At a glance
Internal and external launch coordination playbook covering pre-launch, launch day, and post-launch with run-of-show, comms, RACI, rollback, and retro.
- Works in 4 steps: Kickoff at T-30. Confirm date, launch… → Assign the RACI within 48 hours — every… → Build and sign off the five artifacts… → …
- Coordinate a GA launch
- SKILL.md covers Overview, Core Capabilities, When to Use and Clarify First, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Launch Playbook is an agent skill from borghei/Claude-Skills. 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.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files, including reference files and assets (for example `assets/external-comms-checklist.md`, `assets/internal-comms-plan.md` and `assets/launch-run-of-show.md`).
It sits in DevOps & Cloud. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.
When your agent uses it
- Coordinate a GA launch
Example prompts
- “/launch-playbook”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Kickoff at T-30. Confirm date, launch type, and exec sponsor; open the run-of-show and internal comms plan assets.
- Assign the RACI within 48 hours — every workstream named.
- Build and sign off the five artifacts before T-7; test the rollback drill by T-7.
- Go/no-go at T-3, run launch day from one run-of-show, stabilize T+1 to T+7, run the 30-day retro.
What it can do on your machine
Read from SKILL.md and the folder at commit 4a698e8. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Launch Playbook loads about 1.8k tokens when it runs, and up to ~11k if it reads all its reference files. Until then it costs about 57 tokens; SKILL.md has 825 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 825 words, ~1,778 tokens.
Download SKILL.mdSave it as
.claude/skills/launch-playbook/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.- name
- launch-playbook
- description
- 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.
- license
- MIT + Commons Clause
- metadata.version
- 1.0.1
- metadata.author
- borghei
- metadata.category
- project-management
- metadata.domain
- pm-execution
- metadata.updated
- 2026-06-15
- metadata.tech-stack
- launch, three-launches, dark-launch, raci, progressive-rollout
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.
When NOT to use: continuous-delivery bug fixes and minor improvements (use release-notes/ only); internal-only changes with no external comms (use a release runbook); product sunsets and deprecations (use eol-communication/).
Clarify First
Before building the launch plan, confirm these inputs. If any is unknown or vague, ASK — do not assume:
- Launch date (T-0) — anchors the entire T-30→T+30 timeline and every artifact deadline
- Launch type — big bang / progressive rollout / dark launch drives the run-of-show and the rollback plan
- Cross-functional owners (RACI) — every workstream named across PM/Eng/PMM/Sales/Support/Legal; a missing owner is the #1 cause of failed launches
- Exec sponsor — holds go/no-go authority and receives the T-1/T+1/T+7/T+30 updates
Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.
Quick Start
- Kickoff at T-30. Confirm date, launch type, and exec sponsor; open the run-of-show and internal comms plan assets.
- Assign the RACI within 48 hours — every workstream named.
- Build and sign off the five artifacts before T-7; test the rollback drill by T-7.
- Go/no-go at T-3, run launch day from one run-of-show, stabilize T+1 to T+7, run the 30-day retro.
Full timeline tables, RACI matrix, launch-type rules, and the 10-step workflow are in references/launch-timeline-and-execution.md.
Show full SKILL.md (357 more words)Show less
References
references/launch-timeline-and-execution.md— read this when planning/running the launch: three-launches framework, full T-30→T+30 timeline, launch-type selection, RACI matrix, 10-step workflow, troubleshooting, and success criteria.references/launch-coordination-guide.md— read this for the reasoning behind the playbook: three-launches sequencing, RACI worked examples, big-bang vs progressive decision rules, and anti-patterns.references/red-flags.md— read this before signing off any launch artifact: common failure modes with bad/good examples and fixes.assets/launch-run-of-show.md— hourly run-of-show template for launch day.assets/internal-comms-plan.md— pre-launch, launch-day, and post-launch internal comms templates.assets/external-comms-checklist.md— T-30 to T-0 checklist for press, blog, social, email, sales enablement, support training, and legal review.assets/rollback-plan.md— rollback decision matrix, drill checklist, and execution runbook template.assets/post-launch-retro.md— 7-day and 30-day retrospective template.- Cagan, Marty. Inspired: How to Create Tech Products Customers Love. Wiley, 2018.
Scope & Limitations
In Scope: GA launch coordination across Engineering, Product, PMM, Sales, Support, Legal; run-of-show, rollback plan, comms plans, post-launch retrospective; big bang, progressive rollout, and dark launch patterns; T-30 to T+30 timeline; RACI assignment for cross-functional launches.
Out of Scope: Beta program execution (beta-program/); release notes content generation (release-notes/); end-of-life / sunset communication (eol-communication/); incident response runbooks (delivery-manager/ and engineering on-call); marketing campaign performance analysis beyond the 30-day window (handoff to demand gen).
Important Caveats: A launch is not a moment; it is a 60-day window (T-30 to T+30) -- staff accordingly. The single most common cause of failed launches is a missing RACI assignment, not a missing artifact: if you can name the artifact but not the owner, the artifact will not exist. Big-bang launches concentrate risk on one date; default to progressive rollout unless marketing leverage justifies the risk.
Integration Points
| Integration | Direction | What Flows |
|---|---|---|
beta-program/ | Receives from | Greenlit beta hands off testimonials, known issues, and pricing decision |
create-prd/ | Receives from | PRD provides positioning, segments, and v1 scope |
release-notes/ | Feeds into | Launch produces the GA release notes |
daci-framework/ | Uses | Major launch decisions (go/no-go, rollback) use DACI |
eol-communication/ | Complementary | Launches that replace older features trigger sunset comms |
delivery-manager/ | Uses | Deployment, on-call rota, and rollback execution |
senior-pm/ | Reports to | Exec sponsor receives T-1, T+1, T+7, T+30 updates |
summarize-meeting/ | Feeds into | War-room standups and retro produce structured summaries |
status-update-generator/ | Feeds into | Post-launch metrics roll up into weekly status |
© borghei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 9 other files (references, assets) in project-management/execution/launch-playbook of borghei/Claude-Skills.
- SKILL.md
- assets/external-comms-checklist.md
- assets/internal-comms-plan.md
- assets/launch-run-of-show.md
- assets/post-launch-retro.md
- assets/rollback-plan.md
- examples/shared-dashboards-ga-launch.md
- references/launch-coordination-guide.md
- references/launch-timeline-and-execution.md
- references/red-flags.md
Open the folder on GitHubat commit 4a698e8
Compare with similar skills
Launch Playbook next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Launch Playbook this skillborghei/Claude-Skills | 881 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Release Engineeringmajiayu000/spellbook | 286 | — | ~511 | Automated safety check: Pass | MIT | |
| Monitor CInrwl/nx | 29k | 6 repos | ~4.7k | Automated safety check: Pass | MIT | |
| Repo Hygiene Scan and FixQwenLM/qwen-code | 28k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Bash Defensive Patternspromovaweb/setupvibe | 101 | 15 repos | ~572 | Automated safety check: Pass | GPL-3.0 | |
| Terravision Cloud Diagramspatrickchugh/terravision | 1.6k | — | ~5.6k | Automated safety check: Notes | AGPL-3.0-only |
Similar skills
Monitor CI
nrwl/nx
Monitor Nx Cloud CI pipeline and handle self-healing fixes. An agent skill from nrwl/nx.
Repo Hygiene Scan and Fix
QwenLM/qwen-code
Scheduled CI skill that scans a repository for small, certain docs, test and code hygiene issues and fixes them on one branch with a commit per finding.
Bash Defensive Patterns
promovaweb/setupvibe
Master defensive Bash programming techniques for production-grade scripts.
Terravision Cloud Diagrams
patrickchugh/terravision
Draw cloud architecture diagrams for AWS, Azure or GCP with the official provider icon sets, using TerraVision.
Author Migration
nrwl/nx
Author or scope a first-party Nx migration. An agent skill from nrwl/nx.
More from borghei/Claude-Skills
All 349 skills in this repoAgents In The Team
borghei/Claude-Skills
Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.
AI Content Disclosure
borghei/Claude-Skills
Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.
AI Prototyping
borghei/Claude-Skills
Idea to AI-generated prototype to customer validation to engineering handoff.
Analytics Engineer
borghei/Claude-Skills
Analytics engineering across data modeling, dbt, transformation, and semantic layers.
Ansoff Matrix
borghei/Claude-Skills
Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.
Brainstorm Okrs
borghei/Claude-Skills
OKR brainstorming and validation using the Radical Focus framework — outcome objectives, measurable key results, counter-metrics.
Related
Questions about Launch Playbook
What does Launch Playbook do?
Internal and external launch coordination playbook covering pre-launch, launch day, and post-launch with run-of-show, comms, RACI, rollback, and retro. Launch Playbook is an agent skill from borghei/Claude-Skills. Internal and external launch coordination playbook covering pre-launch, launch day, and post-launch with run-of-show, comms, RACI, rollback, and retro.
When should I use Launch Playbook?
Launch Playbook fits situations like: coordinate a GA launch.
How do I install Launch Playbook in Claude Code?
Run `npx skills add borghei/Claude-Skills --skill launch-playbook -a claude-code`. Or copy the skill folder (project-management/execution/launch-playbook in borghei/Claude-Skills) into .claude/skills/launch-playbook in your project. Claude Code loads it when a task matches its description.
How do I install Launch Playbook in Codex?
Run `npx skills add borghei/Claude-Skills --skill launch-playbook -a codex`. Or copy the skill folder (project-management/execution/launch-playbook in borghei/Claude-Skills) into .agents/skills/launch-playbook in your project. Codex loads it when a task matches its description.
Can I use Launch Playbook in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add borghei/Claude-Skills --skill launch-playbook -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/launch-playbook, .gemini/skills/launch-playbook, .github/skills/launch-playbook and .opencode/skills/launch-playbook in your project.
What does Launch Playbook need to run?
SKILL.md names no scripts, command-line tools or credentials: Launch Playbook is instructions for the agent only.
Does Launch Playbook access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Launch Playbook safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Launch Playbook use?
Launch Playbook is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Launch Playbook use?
About 1.8k tokens (SKILL.md is roughly 7.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 8.9k tokens, read only when the agent opens those files.
What are the alternatives to Launch Playbook?
Skills that share tags, products or a category with Launch Playbook: Release Engineering (majiayu000/spellbook, 286 stars), Monitor CI (nrwl/nx, 29k stars), Repo Hygiene Scan and Fix (QwenLM/qwen-code, 28k stars) and Bash Defensive Patterns (promovaweb/setupvibe, 101 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Launch Playbook?
borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 881 GitHub stars. The repository holds 349 skills in this directory. The repository was last updated on October 7, 2026.
Source: borghei/Claude-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.