Deliver Launch Checklist

Generates a structured pre-launch checklist that covers engineering, QA, design, marketing, support, legal, and ops. You define the launch context and tier, then it helps you gather requirements across functions, assign owners with dates, flag blockers and dependencies, and document go/no-go criteria plus rollback plans. Best used 1-2 weeks before any significant release or during launch planning kickoffs. The real value is forcing you to think through cross-functional coordination before launch day chaos hits. It's basically institutionalized paranoia in checklist form, which is exactly what you need when multiple teams have to ship in sync.

skills.sh installs: 834
GitHub stars: 794
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add product-on-purpose/pm-skills --skill deliver-launch-checklist --agent claude-code

Installs into .claude/skills of the current project.

Files

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-results or iterate-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

SKILL.md on GitHub