Launch Planning Frameworks
slgoodrich/agents
Launch planning frameworks including tiered launches, timelines, checklists, and go/no-go decisions.
Creates a cross-functional pre-launch checklist covering engineering, design, marketing, support, legal, and operations readiness, with owners, dates, and go/no-go criteria so nothing is missed…
Install Deliver Launch Checklist
$ npx skills add product-on-purpose/pm-skills --skill deliver-launch-checklist -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install product-on-purpose/pm-skills deliver-launch-checklist --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/product-on-purpose/pm-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/deliver-launch-checklist .claude/skills/deliver-launch-checklist && 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 "deliver-launch-checklist" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/deliver-launch-checklist into .claude/skills/deliver-launch-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deliver-launch-checklist", 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/product-on-purpose/pm-skills/tree/main/skills/deliver-launch-checklistType 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 product-on-purpose/pm-skills --skill deliver-launch-checklist -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install product-on-purpose/pm-skills deliver-launch-checklist --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/deliver-launch-checklist .agents/skills/deliver-launch-checklist && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "deliver-launch-checklist" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/deliver-launch-checklist into .agents/skills/deliver-launch-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deliver-launch-checklist", 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 product-on-purpose/pm-skills --skill deliver-launch-checklist -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install product-on-purpose/pm-skills deliver-launch-checklist --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/deliver-launch-checklist .cursor/skills/deliver-launch-checklist && 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 "deliver-launch-checklist" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/deliver-launch-checklist into .cursor/skills/deliver-launch-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deliver-launch-checklist", 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/product-on-purpose/pm-skills.git --path skills/deliver-launch-checklist--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 product-on-purpose/pm-skills --skill deliver-launch-checklist -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install product-on-purpose/pm-skills deliver-launch-checklist --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/deliver-launch-checklist .gemini/skills/deliver-launch-checklist && 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 "deliver-launch-checklist" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/deliver-launch-checklist into .gemini/skills/deliver-launch-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deliver-launch-checklist", 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 product-on-purpose/pm-skills deliver-launch-checklistInstalls 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 product-on-purpose/pm-skills --skill deliver-launch-checklist -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/deliver-launch-checklist .github/skills/deliver-launch-checklist && 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 "deliver-launch-checklist" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/deliver-launch-checklist into .github/skills/deliver-launch-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deliver-launch-checklist", 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 product-on-purpose/pm-skills --skill deliver-launch-checklist -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install product-on-purpose/pm-skills deliver-launch-checklist --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/deliver-launch-checklist .opencode/skills/deliver-launch-checklist && 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 "deliver-launch-checklist" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/deliver-launch-checklist into .opencode/skills/deliver-launch-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deliver-launch-checklist", 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
deliver-launch-checklist- GitHub stars
- 716
- Token cost
- ~970 tokens
- SKILL.md length
- 413 words
- Files
- 5 (incl. references)
- Skills in repo
- 68
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Creates a cross-functional pre-launch checklist covering engineering, design, marketing, support, legal, and operations readiness, with owners, dates, and go/no-go criteria so nothing is missed…
- Works in 7 steps: Define Launch Context → Gather Functional Requirements → Assign Owners and Dates → …
- Cross-team launches
- SKILL.md covers When to Use, When NOT to Use, Instructions and Output Format, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Deliver Launch Checklist is an agent skill from product-on-purpose/pm-skills. Creates a cross-functional pre-launch checklist covering engineering, design, marketing, support, legal, and operations readiness, with owners, dates, and go/no-go criteria so nothing is missed before release. Use for significant or cross-team launches, not a small single-team change. For the customer-facing announcement of what shipped, use deliver-release-notes instead.
Its SKILL.md is about 970 tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `HISTORY.md`, `evals/trigger-fixtures.json` and `references/EXAMPLE.md`).
It sits in Marketing & SEO, covering Product launch strategy, Feature launches and release readiness and Changelog and release notes. The repository describes itself as: 68 plug-and-play, best-practice product management skills for AI agents: 30 Triple Diamond phase + 11 foundation + 12 utility + 15 tool (Foundation Sprint + Design Sprint). Plus… The licence is Apache-2.0.
When your agent uses it
- Cross-team launches
- Not a small single-team change
Example prompts
- “Use the deliver-launch-checklist skill to create a cross-functional pre-launch checklist covering engineering, design, marketing, support, legal…”
- “/deliver-launch-checklist”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Define Launch Context
- Gather Functional Requirements
- Assign Owners and Dates
- Identify Dependencies and Blockers
- Define Go/No-Go Criteria
- Document Rollback Plan
- Schedule Check-in Cadence
What it can do on your machine
Read from SKILL.md and the folder at commit 1cef1a9. 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
Deliver Launch Checklist loads about 970 tokens when it runs, and up to ~4.2k if it reads all its reference files. Until then it costs about 100 tokens; SKILL.md has 413 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 product-on-purpose/pm-skills at commit 1cef1a9, republished under its Apache-2.0 licence (© product-on-purpose). 413 words, ~970 tokens.
Download SKILL.mdSave it as
.claude/skills/deliver-launch-checklist/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- deliver-launch-checklist
- description
- Creates a cross-functional pre-launch checklist covering engineering, design, marketing, support, legal, and operations readiness, with owners, dates, and go/no-go criteria so nothing is missed before release. Use for significant or cross-team launches, not a small single-team change. For the customer-facing announcement of what shipped, use deliver-release-notes instead.
- license
- Apache-2.0
- metadata.phase
- deliver
- metadata.version
- 2.2.0
- metadata.updated
- 2026-07-04
- metadata.category
- coordination
- metadata.frameworks
- triple-diamond, lean-startup, design-thinking
- metadata.author
- product-on-purpose
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->Launch Checklist
A launch checklist is a comprehensive verification document that ensures all functions are ready before releasing a feature or product. It coordinates across engineering, QA, design, marketing, support, legal, and operations to prevent launch-day surprises. Good launch checklists surface blockers early and create shared accountability for launch readiness.
When to Use
- 1-2 weeks before any significant launch
- During launch planning kickoff meetings
- When coordinating cross-functional releases
- Before major version releases or feature rollouts
- After incidents to improve launch processes
When NOT to Use
- You are validating whether to ship at all via an experiment -> use
measure-experiment-design - You need the customer-facing announcement of what shipped -> use
deliver-release-notes - The launch already happened and you want results or reflection -> use
measure-experiment-resultsoriterate-retrospective - The change is small and single-team with no cross-functional surface: a launch checklist adds ceremony without value; track it in the sprint instead
Instructions
When asked to create a launch checklist, follow these steps:
Define Launch Context Document what is launching, when, and who the key stakeholders are. Establish the launch tier (major release, minor feature, experiment) as this affects checklist scope.
Gather Functional Requirements For each function (engineering, QA, marketing, etc.), identify what must be complete, verified, or in place before launch. Distinguish between blockers (must-have) and nice-to-haves.
Assign Owners and Dates Every checklist item needs an owner and a target completion date. Ownership creates accountability; dates enable tracking.
Identify Dependencies and Blockers Flag items that block other work or are blocked by external factors. Surface these early so teams can unblock.
Define Go/No-Go Criteria Establish clear criteria for making the launch decision. What conditions must be met? Who makes the final call?
Document Rollback Plan Every launch should have a rollback strategy. Document how to revert if critical issues emerge post-launch.
Schedule Check-in Cadence Establish when the team will review checklist progress (daily standups, T-2 days review, launch day sync).
Show full SKILL.md (92 more words)Show less
Output Format
Use the template in references/TEMPLATE.md to structure the output. A complete checklist fills every template section: Launch Overview; Engineering Readiness; QA & Testing; Design & UX; Marketing & Communications; Customer Support; Legal & Compliance; Operations & Infrastructure; Analytics & Monitoring; Go/No-Go Criteria; Rollback Plan; Check-in Schedule; and Open Issues.
Quality Checklist
Before finalizing, verify:
- All functional areas are represented
- Every item has an owner and target date
- Blockers are clearly distinguished from nice-to-haves
- Go/No-Go criteria are specific and measurable
- Rollback plan is documented and tested
- Check-in cadence is scheduled
Examples
See references/EXAMPLE.md for a completed example.
© product-on-purpose, Apache-2.0. 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 4 other files (references) in skills/deliver-launch-checklist of product-on-purpose/pm-skills.
- SKILL.md
- HISTORY.md
- evals/trigger-fixtures.json
- references/EXAMPLE.md
- references/TEMPLATE.md
Open the folder on GitHubat commit 1cef1a9
Compare with similar skills
Deliver Launch Checklist 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 |
|---|---|---|---|---|---|---|
| Deliver Launch Checklist this skillproduct-on-purpose/pm-skills | 716 | — | ~970 | Automated safety check: Pass | Apache-2.0 | |
| Launch Planning Frameworksslgoodrich/agents | 139 | — | ~3.2k | Automated safety check: Pass | Custom licence | |
| Launch Registryaaron-he-zhu/aaron-marketing-skills | 2.9k | 1 repos | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Launch Readiness Auditoraaron-he-zhu/aaron-marketing-skills | 2.9k | — | ~2k | Automated safety check: Pass | Apache-2.0 | |
| Early Access Designeraaron-he-zhu/aaron-marketing-skills | 2.9k | — | ~3.4k | Automated safety check: Pass | Apache-2.0 | |
| Feature Launch Playbookgooseworks-ai/goose-skills | 1.2k | 1 repos | ~1.8k | Automated safety check: Pass | MIT |
Similar skills
Launch Registry
aaron-he-zhu/aaron-marketing-skills
A skill your agent uses when the user asks to "log this launch", query a launch date/embargo, record a stage transition, or update submissions/outcomes; curates launch facts through the append-only…
Launch Readiness Auditor
aaron-he-zhu/aaron-marketing-skills
A skill your agent uses when the user asks to "audit our launch plan", "are we ready to launch", or evaluate launch execution/outcomes; runs one typed RAMP preflight, execution, or outcome profile…
Early Access Designer
aaron-he-zhu/aaron-marketing-skills
A skill your agent uses when the user asks to "design an early access program", "set up a waitlist and beta stages", or "define beta graduation criteria"; produces a waitlist→concept→alpha→beta→GA…
Feature Launch Playbook
gooseworks-ai/goose-skills
Take a new feature or product update and generate the full launch kit: changelog entry, email announcement, LinkedIn post variants, in-app banner text, Twitter/X thread, and internal sales…
Mvp Launch
ooiyeefei/ccc
Web app MVP launch checklist knowledge. An agent skill from ooiyeefei/ccc.
More from product-on-purpose/pm-skills
All 68 skills in this repoDefine Hypothesis
product-on-purpose/pm-skills
Defines a testable hypothesis with clear success metrics and a validation approach.
Define Jtbd Canvas
product-on-purpose/pm-skills
Creates a Jobs to be Done canvas capturing the functional, emotional, and social dimensions of a customer job.
Define Opportunity Tree
product-on-purpose/pm-skills
Creates an opportunity solution tree connecting a desired outcome to customer opportunities and candidate solutions, preventing solution-first jumps in continuous discovery.
Define Problem Statement
product-on-purpose/pm-skills
Creates a clear problem framing document with user impact, business context, and success criteria.
Deliver Acceptance Criteria
product-on-purpose/pm-skills
Generates structured Given/When/Then acceptance criteria for a user story or feature slice, covering the happy path, key failure scenarios, and non-functional expectations in testable form.
Deliver Prd
product-on-purpose/pm-skills
Creates a comprehensive Product Requirements Document that aligns stakeholders on what to build, why, and how success will be measured.
Related
Categories
Questions about Deliver Launch Checklist
What does Deliver Launch Checklist do?
Creates a cross-functional pre-launch checklist covering engineering, design, marketing, support, legal, and operations readiness, with owners, dates, and go/no-go criteria so nothing is missed…. Deliver Launch Checklist is an agent skill from product-on-purpose/pm-skills. Creates a cross-functional pre-launch checklist covering engineering, design, marketing, support, legal, and operations readiness, with owners, dates, and go/no-go criteria so nothing is missed before release.
When should I use Deliver Launch Checklist?
Deliver Launch Checklist fits situations like: cross-team launches; not a small single-team change.
How do I install Deliver Launch Checklist in Claude Code?
Run `npx skills add product-on-purpose/pm-skills --skill deliver-launch-checklist -a claude-code`. Or copy the skill folder (skills/deliver-launch-checklist in product-on-purpose/pm-skills) into .claude/skills/deliver-launch-checklist in your project. Claude Code loads it when a task matches its description.
How do I install Deliver Launch Checklist in Codex?
Run `npx skills add product-on-purpose/pm-skills --skill deliver-launch-checklist -a codex`. Or copy the skill folder (skills/deliver-launch-checklist in product-on-purpose/pm-skills) into .agents/skills/deliver-launch-checklist in your project. Codex loads it when a task matches its description.
Can I use Deliver Launch Checklist 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 product-on-purpose/pm-skills --skill deliver-launch-checklist -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/deliver-launch-checklist, .gemini/skills/deliver-launch-checklist, .github/skills/deliver-launch-checklist and .opencode/skills/deliver-launch-checklist in your project.
What does Deliver Launch Checklist need to run?
SKILL.md names no scripts, command-line tools or credentials: Deliver Launch Checklist is instructions for the agent only.
Does Deliver Launch Checklist 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 Deliver Launch Checklist 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 Deliver Launch Checklist use?
Deliver Launch Checklist is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Deliver Launch Checklist use?
About 970 tokens (SKILL.md is roughly 3.9k 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 3.2k tokens, read only when the agent opens those files.
What are the alternatives to Deliver Launch Checklist?
Skills that share tags, products or a category with Deliver Launch Checklist: Launch Planning Frameworks (slgoodrich/agents, 139 stars), Launch Registry (aaron-he-zhu/aaron-marketing-skills, 2.9k stars), Launch Readiness Auditor (aaron-he-zhu/aaron-marketing-skills, 2.9k stars) and Early Access Designer (aaron-he-zhu/aaron-marketing-skills, 2.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Deliver Launch Checklist?
product-on-purpose (a GitHub organization) maintains it in product-on-purpose/pm-skills, which has 716 GitHub stars. The repository holds 68 skills in this directory. The repository was last updated on October 8, 2026.
Source: product-on-purpose/pm-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.