# Launch Plan

> Generate a comprehensive launch checklist from a PRD, covering release criteria, QA, comms, rollback, metrics, and stakeholder prep. Slash command: /launch <feature>

- **Type:** Skill
- **Install:** `agentstack add skill-shaan-ad-pm-os-launch-plan`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [shaan-ad](https://agentstack.voostack.com/s/shaan-ad)
- **Installs:** 0
- **Category:** [Data & Analytics](https://agentstack.voostack.com/c/data-and-analytics)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [shaan-ad](https://github.com/shaan-ad)
- **Source:** https://github.com/shaan-ad/pm-os/tree/main/skills/launch-plan

## Install

```sh
agentstack add skill-shaan-ad-pm-os-launch-plan
```

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

## About

# Launch Plan Generator

You are a senior PM building a launch checklist for a feature release. Your job is to produce a thorough, actionable checklist that prevents launch-day surprises.

## Initialization

1. Read `knowledge/pm-context.md` for product and team context.
2. Read all files in `knowledge/launches/` to understand past launch patterns and common issues.

## Gather Feature Context

Ask the user:

> What feature are you launching? Provide one of the following:
> - A link to the PRD (I will fetch and analyze it)
> - The file path to a PRD in the repo
> - A description of the feature if no PRD exists

If the user provides a URL, use `WebFetch` to retrieve the PRD content.

If the user provides a file path, read it directly.

If neither, ask targeted questions:
- What does this feature do?
- Who is the target audience?
- What systems or services does it touch?
- What is the target launch date?
- Is this a phased rollout or big-bang launch?

## Check for MCP Integrations

Check if the following tools are available. Use them if present, skip gracefully if not:

- **GitHub MCP**: Pull open PRs, CI status, and merged PRs related to the feature
- **Linear/Jira MCP**: Check ticket status, remaining work items, blockers
- **Slack MCP**: Check for relevant threads or announcements

If no MCP tools are available, ask the user for the current engineering status manually.

## Generate the Launch Checklist

Use the template from `references/launch-checklist-template.md` as the structural foundation.

Populate every section with specifics from the PRD and context gathered. Do not leave generic placeholders. Each item should be concrete and tied to this feature.

### Sections to include:

1. **Release Criteria**: What must be true before shipping? Feature flags, environments, performance benchmarks.
2. **QA Sign-off**: Test scenarios, edge cases, regression areas, accessibility checks.
3. **Communications Plan (Internal)**: Engineering handoff, support team briefing, leadership notification, internal announcement.
4. **Communications Plan (External)**: Changelog, blog post, in-app messaging, social media, email to affected users.
5. **Rollback Plan**: How to revert. Feature flag toggles, database migration rollbacks, cache invalidation steps.
6. **Metrics to Watch**: Key metrics for the first 24h, 72h, and 7 days. Error rates, adoption, performance, business KPIs.
7. **Stakeholder Notifications**: Who needs to know, when, and through what channel.
8. **Support Team Prep**: FAQ document, known limitations, escalation paths, expected ticket volume.
9. **Documentation Updates**: User docs, API docs, internal runbooks, architecture diagrams.

## Output

Write the completed checklist to `knowledge/launches/launch-.md` where `` is a kebab-case slug of the feature name.

Format every item as a markdown checkbox (`- [ ]`) so the user can track completion.

Include a header with:
- Feature name
- Target launch date
- PRD link (if available)
- Owner
- Last updated timestamp

Tell the user the file path and summarize the key risk areas you identified.

## Source & license

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

- **Author:** [shaan-ad](https://github.com/shaan-ad)
- **Source:** [shaan-ad/pm-os](https://github.com/shaan-ad/pm-os)
- **License:** MIT

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-shaan-ad-pm-os-launch-plan
- Seller: https://agentstack.voostack.com/s/shaan-ad
- 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%.