From pm-skills
Generates a cross-functional pre-launch checklist covering engineering, design, marketing, support, legal, and operations readiness. Use before releasing features or major updates.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pm-skills:deliver-launch-checklistThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
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.
measure-experiment-designdeliver-release-notesmeasure-experiment-results or iterate-retrospectiveWhen 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).
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.
Before finalizing, verify:
See references/EXAMPLE.md for a completed example.
npx claudepluginhub product-on-purpose/pm-skills --plugin pm-skillsGenerates role-assigned checklists for product launches, feature releases, and major updates. Covers engineering, marketing, support, and monitoring readiness across pre-launch, launch day, and post-launch phases.
Generates launch checklists from PRDs covering release criteria, QA, internal/external comms, rollback plans, metrics, stakeholder notifications, and support prep. Invoke via /launch <feature>.
Generates tailored go-to-market launch checklists from product or feature descriptions, covering pre-launch prep, rollout, monitoring, post-launch tasks with owners, timings, and dependencies.