# Deliver Launch Checklist

> Creates a comprehensive pre-launch checklist covering engineering, design, marketing, support, legal, and operations readiness. Use before releasing features, products, or major updates to ensure nothing is missed.

- **Type:** Skill
- **Install:** `agentstack add skill-product-on-purpose-pm-skills-deliver-launch-checklist`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [product-on-purpose](https://agentstack.voostack.com/s/product-on-purpose)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** Apache-2.0
- **Upstream author:** [product-on-purpose](https://github.com/product-on-purpose)
- **Source:** https://github.com/product-on-purpose/pm-skills/tree/main/skills/deliver-launch-checklist
- **Website:** https://product-on-purpose.github.io/pm-skills/

## Install

```sh
agentstack add skill-product-on-purpose-pm-skills-deliver-launch-checklist
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# 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

## Instructions

When asked to create a launch checklist, follow these steps:

1. **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.

2. **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.

3. **Assign Owners and Dates**
   Every checklist item needs an owner and a target completion date. Ownership creates accountability; dates enable tracking.

4. **Identify Dependencies and Blockers**
   Flag items that block other work or are blocked by external factors. Surface these early so teams can unblock.

5. **Define Go/No-Go Criteria**
   Establish clear criteria for making the launch decision. What conditions must be met? Who makes the final call?

6. **Document Rollback Plan**
   Every launch should have a rollback strategy. Document how to revert if critical issues emerge post-launch.

7. **Schedule Check-in Cadence**
   Establish when the team will review checklist progress (daily standups, T-2 days review, launch day sync).

## 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.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [product-on-purpose](https://github.com/product-on-purpose)
- **Source:** [product-on-purpose/pm-skills](https://github.com/product-on-purpose/pm-skills)
- **License:** Apache-2.0
- **Homepage:** https://product-on-purpose.github.io/pm-skills/

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-product-on-purpose-pm-skills-deliver-launch-checklist
- Seller: https://agentstack.voostack.com/s/product-on-purpose
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.