# Launch Plan

> Build a coordinated product/marketing launch plan with messaging, assets, milestones, instrumentation, and post-launch review.

- Skill: `45ck/launch-plan` (Agent Skill)
- Install (CLI): `npx skillmds@latest add 45ck/launch-plan`
- Raw SKILL.md: https://api.skillmd.com/api/skills/45ck/launch-plan/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Marketing & Growth
- Author: 45ck (https://skillmd.com/u/45ck)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/45ck/launch-plan

---


# Launch Plan

Use this skill when the user wants a structured plan for launching a new feature, product, campaign, or GTM motion.

## What this skill must produce

Always produce:

1. **Launch summary**
2. **Audience / segmentation**
3. **Core message**
4. **Asset checklist**
5. **Launch timeline**
6. **Measurement plan**
7. **Risk register**
8. **Post-launch review plan**

## Inputs to gather

If possible, extract:
- what is launching
- who it is for
- problem solved
- launch type (beta / GA / pricing / category / lifecycle / campaign)
- business goal
- launch date
- stakeholders
- dependencies
- channels
- available proof / assets

If some are missing, infer and label assumptions.

## Working rules

- Tie launch activity to a clear customer problem and target audience.
- Ensure product, marketing, sales, success, and analytics are aligned where relevant.
- Include both pre-launch readiness and post-launch measurement.
- Do not treat launch as only a publishing event; include enablement and feedback loops.

## Step-by-step method

### Step 1: define the launch
State:
- what is launching
- for whom
- why now
- what should happen if launch succeeds

### Step 2: define audience slices
Segment:
- who should hear about it first
- who should not
- who needs a tailored version of the message

### Step 3: define core narrative
Write:
- one-sentence positioning for the launch
- key benefits
- proof
- objections

### Step 4: identify channels and assets
List what is needed for:
- homepage / landing page
- product UI
- lifecycle email
- social
- sales enablement
- support / success enablement
- docs / help center
- changelog / release notes

### Step 5: define timeline
Split into:
- pre-launch
- launch day
- post-launch week 1-2
- post-launch month 1

### Step 6: define metrics
Include:
- awareness metrics
- adoption metrics
- activation / usage metrics
- revenue / pipeline metrics if relevant
- qualitative feedback

### Step 7: define review cadence
Plan post-launch reviews and decisions.

## Output structure

### Launch summary
- Launch:
- Type:
- Audience:
- Goal:
- Success looks like:

### Audience / segmentation
| Segment | Why they care | Message angle | Channel |
|---|---|---|---|

### Core message
- One-liner:
- Headline:
- 3 key benefits:
- Proof points:
- Main objection and response:

### Asset checklist
| Asset | Owner | Needed by | Status |
|---|---|---|---|

### Launch timeline
| When | Action | Owner | Dependency |
|---|---|---|---|

### Measurement plan
| Metric | Why it matters | Owner | Review cadence |
|---|---|---|---|

### Risk register
| Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|

### Post-launch review plan
- 24h review:
- 7-day review:
- 30-day review:
- launch questions to answer:
- go / iterate / rollback criteria:

## Special instructions

If the launch is for a PLG feature:
- include in-product announcement and lifecycle messaging
- define product-qualified behavior
- include self-serve conversion and team expansion signals

If the launch is enterprise-facing:
- include sales enablement, objection handling, and customer-success briefing