deliver-launch-checklist SKILL.md skillA
deliver-launch-checklist from product-on-purpose/pm-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add product-on-purpose/pm-skills/deliver-launch-checklist@v2.2.0Pins v2.2.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- product-on-purpose/pm-skills
- Path
skills/deliver-launch-checklist/SKILL.md- Versions recorded
- 5
- Latest version
- v2.2.0, committed Jul 5, 2026
- First version recorded
- Jan 27, 2026
- Size
- 3,877 bytes
- Repository stars
- 790
- License
- Apache-2.0
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.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
<!-- 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-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 …
Read the whole file at its exact version.
How to install
mdr add product-on-purpose/pm-skills/deliver-launch-checklist@sha256:12e1baee7add28b6The line at the top of this page pins the label v2.2.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_7k6lzbvn2twvlnvs)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jan 27, 2026 and Jul 5, 2026, about one every 40 days. Its first recorded version is graded C and its latest A.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v2.2.0 latest | 2026-07-05 | 87e423c | 3,877 B | A | view · diff |
| v2.1.0 | 2026-06-10 | bf23914 | 3,717 B | A | view · diff |
| v2.0.0 | 2026-05-20 | be1352b | 2,922 B | A | view · diff |
| v2.0.0 | 2026-03-25 | 0ab0a60 | 2,916 B | A | view · diff |
| git:20260127.ac99454 | 2026-01-27 | ac99454 | 2,916 B | C | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3877 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
product-on-purpose/pm-skills · 790 stars · license Apache-2.0 · pushed 2026-11-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7k6lzbvn2twvlnvs GET https://markdownregistry.com/api/v1/resolve?ref=product-on-purpose/pm-skills/deliver-launch-checklist GET https://markdownregistry.com/api/v1/blob/12e1baee7add28b64184c46b570869e59d708938d00a7d2f355c54fdae90f059
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.