Skip to content

deanpeters/Product-Manager-Skills / plugins/pm-deliver/skills/launch-plan

launch-plan

Verified

Build a launch plan sized by tier: owners, dates, go/no-go criteria, and a readiness scorecard. Use when a launch needs every function ready at once and nobody has defined 'ready'.

FileKindSize
SKILL.mdskill md22.5 KB
examples/sample-industrial.mdmarkdown4.6 KB
examples/sample.mdmarkdown4.4 KB
template.mdmarkdown3.5 KB

template.md

View on GitHub
# Launch Plan Template

Fill the tier first. It sizes everything below. Every unsupplied date, owner, quantity, or
threshold stays `[NEEDS SOURCE]`. Quality checks at the bottom.

---

## 1. Tier assessment

| Criterion | Low / Med / High | One-line reason |
|---|---|---|
| Revenue and margin at stake | | |
| Newness to the customer | | |
| Newness to the company | | |
| Regulatory and safety exposure | | |
| Installed-base impact | | |
| Channel impact | | |

**Proposed tier:** [1 Full / 2 Standard / 3 Light] · **Why:** [one line]
**A lighter tier would leave uncovered:** [name the rows]
**Confirmed by:** [forum, date]

## 2. The four dates

| Moment | Date | Gap to the next, and why it is acceptable |
|---|---|---|
| Announce | | |
| Order opens | | |
| First delivery | | |
| Full support | | |

**Fixed date driving the plan:** [event, contract, season, budget year]
**Critical-path lead times:** [certification, tooling, translation, partner price-list deadlines, security review]

## 3. Checklist by function

| Function | Deliverable ("done" in one line) | Owner (named) | Due | Status | Tag |
|---|---|---|---|---|---|
| Sales and channel | | | | | |
| Support / Service / spare parts | | | | | |
| Operations / production | | | | | |
| Pricing and commercial | | | | | |
| Legal / compliance | | | | | |
| Documentation and training | | | | | |
| Marketing | | | | | |
| Internal enablement | | | | | |

Status: Not started · On track · At risk · Done · Not applicable (with a reason).
Tag: `[FROM YOU]` · `[RESEARCH]` · `[AI-SUGGESTED, VALIDATE THIS]`.

## 4. Go/no-go criteria (written before the gate)

| # | What is checked | Threshold | Evidence | Owner | Must-pass or Watch |
|---|---|---|---|---|---|

**Gates:** [name, date, Approver] · [name, date, Approver]
**DACI per gate:** Driver [ ] · Approver [one person] · Contributors [ ] · Informed [ ]

## 5. Launch Readiness Scorecard

Status definitions (written before the first review):
- **Ready:** [what evidence exists]
- **At risk:** [what is missing or unconfirmed]
- **Not ready:** [what is missing and has no plan]

| Function | Readiness criteria | Status | Owner | Evidence | Must-pass? | RACI |
|---|---|---|---|---|---|---|

**Scorecard verdict rule:** any must-pass "Not ready" means no-go.

## 6. Risks and dependencies

| Risk | Cause / trigger | Consequence | Response | Owner | Exposure remaining |
|---|---|---|---|---|---|

## 7. Premortem record

**Scene:** "It is [horizon] after launch and it failed."

| Failure story (by function owner) | Cause | Likelihood / Impact | Landed as (criterion # / risk) |
|---|---|---|---|

## 8. Pre-approval check

| Point | Holds? | Gap named (not filled) |
|---|---|---|
| Owners (delivery, adoption, operation, measurement) | | |
| Dependencies and critical path | | |
| Risks fully specified | | |
| Adoption owned | | |
| Evidence, not just dates | | |
| Rollback and pause conditions | | |

## 9. Riskiest assumptions (committed copy)
1. [the AI-suggested row or unagreed date that would most hurt if wrong]

---

## Quality checks
- [ ] Tier stated with scores, a lighter-tier trade-off named, and confirmed by the forum
- [ ] All four dates present, and each gap is a decision
- [ ] Every row has a named owner who agreed the date
- [ ] Support (and spare parts, if hardware) has its own dated milestone
- [ ] Go/no-go criteria are measurable, owned, and marked must-pass or watch, written before status
- [ ] One approver per gate
- [ ] Every "Ready" cites evidence
- [ ] Every premortem driver landed in the plan
- [ ] No invented dates, quantities, or owners
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall