Create Launch Plan
Requirements
What's being launched, target launch date, launch tier (major/significant/incremental), target audience, key value proposition
2
Gather launch context:
- What are we launching? (Product, feature, update)
- When is the target launch date?
- What tier is this? (Tier 1: major, Tier 2: significant feature, Tier 3: incremental)
- Who is the primary audience?
- What's the key message or value proposition?
- Any constraints? (Budget, resources, dependencies)
If user is unsure about tier, help them decide based on scope and impact.
3
Generate the Launch Brief:
# Launch Plan: [Product/Feature Name]
## Overview
**Launch Date:** [Date]
**Launch Tier:** [1/2/3]
**Owner:** [TBD]
## What We're Launching
[2-3 sentence description]
## Why It Matters
[Customer problem it solves, business impact]
## Target Audience
- Primary: [Segment]
- Secondary: [Segment]
## Key Messages
1. [Primary message]
2. [Supporting message]
3. [Differentiator]
## Success Metrics
| Metric | Target | Measurement |
|--------|--------|-------------|
| [Metric 1] | [Target] | [How we'll measure] |
| [Metric 2] | [Target] | [How we'll measure] | 4
Generate the Timeline (adjust based on tier):
## Launch Timeline
### Phase 1: Strategy [Dates]
- [ ] Positioning finalized
- [ ] Launch tier confirmed
- [ ] Success metrics defined
- [ ] Stakeholder alignment meeting
- [ ] Timeline approved
### Phase 2: Preparation [Dates]
- [ ] Blog post drafted
- [ ] Email copy written
- [ ] Social content created
- [ ] Sales enablement updated
- [ ] Support briefed
- [ ] All assets approved
### Phase 3: Staging [Dates]
- [ ] All content scheduled
- [ ] QA complete
- [ ] Final stakeholder sync
- [ ] Contingency plan reviewed
### Phase 4: Launch Day [Date]
- [ ] Go live!
- [ ] Monitor channels
- [ ] War room active
### Phase 5: Post-Launch [Dates]
- [ ] Day 1 metrics check
- [ ] Week 1 retro
- [ ] Learnings documented 5
Generate the RACI Matrix:
## Roles and Responsibilities
| Activity | Responsible | Accountable | Consulted | Informed |
|----------|-------------|-------------|-----------|----------|
| Positioning | Marketing | PM | Sales | Exec |
| Blog post | Marketing | Marketing | PM | All |
| Sales enablement | Marketing | Sales Lead | Sales | Support |
| Support docs | Support | Support Lead | PM | Marketing |
| Go/No-go decision | PM | Exec | All | All |Customize based on the user's team structure and launch tier.
6
Summarize the launch plan and offer next steps:
- "Want me to create a detailed checklist for each phase?"
- "Need stakeholder communication templates?"
- "Should I draft announcement copy for your channels?"
The plan is ready to share with the team for feedback and owner assignment.
To run this task you must have the following required information:
> What's being launched, target launch date, launch tier (major/significant/incremental), target audience, key value proposition
If you don't have all of this information, exit here and respond asking for any extra information you require, and instructions to run this task again with ALL required information.
---
You MUST use a todo list to complete these steps in order. Never move on to one step if you haven't completed the previous step. If you have multiple read steps in a row, read them all at once (in parallel).
Add all steps to your todo list now and begin executing.
## Steps
1. [Read Launch Planning Framework]: Read the documentation in: `./skills/sauna/[skill_id]/references/marketing.launch.framework.md` (Get launch phases, timeline templates, and stakeholder roles)
2. Gather launch context:
- What are we launching? (Product, feature, update)
- When is the target launch date?
- What tier is this? (Tier 1: major, Tier 2: significant feature, Tier 3: incremental)
- Who is the primary audience?
- What's the key message or value proposition?
- Any constraints? (Budget, resources, dependencies)
If user is unsure about tier, help them decide based on scope and impact.
3. Generate the Launch Brief:
```markdown
# Launch Plan: [Product/Feature Name]
## Overview
**Launch Date:** [Date]
**Launch Tier:** [1/2/3]
**Owner:** [TBD]
## What We're Launching
[2-3 sentence description]
## Why It Matters
[Customer problem it solves, business impact]
## Target Audience
- Primary: [Segment]
- Secondary: [Segment]
## Key Messages
1. [Primary message]
2. [Supporting message]
3. [Differentiator]
## Success Metrics
| Metric | Target | Measurement |
|--------|--------|-------------|
| [Metric 1] | [Target] | [How we'll measure] |
| [Metric 2] | [Target] | [How we'll measure] |
```
4. Generate the Timeline (adjust based on tier):
```markdown
## Launch Timeline
### Phase 1: Strategy [Dates]
- [ ] Positioning finalized
- [ ] Launch tier confirmed
- [ ] Success metrics defined
- [ ] Stakeholder alignment meeting
- [ ] Timeline approved
### Phase 2: Preparation [Dates]
- [ ] Blog post drafted
- [ ] Email copy written
- [ ] Social content created
- [ ] Sales enablement updated
- [ ] Support briefed
- [ ] All assets approved
### Phase 3: Staging [Dates]
- [ ] All content scheduled
- [ ] QA complete
- [ ] Final stakeholder sync
- [ ] Contingency plan reviewed
### Phase 4: Launch Day [Date]
- [ ] Go live!
- [ ] Monitor channels
- [ ] War room active
### Phase 5: Post-Launch [Dates]
- [ ] Day 1 metrics check
- [ ] Week 1 retro
- [ ] Learnings documented
```
5. Generate the RACI Matrix:
```markdown
## Roles and Responsibilities
| Activity | Responsible | Accountable | Consulted | Informed |
|----------|-------------|-------------|-----------|----------|
| Positioning | Marketing | PM | Sales | Exec |
| Blog post | Marketing | Marketing | PM | All |
| Sales enablement | Marketing | Sales Lead | Sales | Support |
| Support docs | Support | Support Lead | PM | Marketing |
| Go/No-go decision | PM | Exec | All | All |
```
Customize based on the user's team structure and launch tier.
6. Summarize the launch plan and offer next steps:
- "Want me to create a detailed checklist for each phase?"
- "Need stakeholder communication templates?"
- "Should I draft announcement copy for your channels?"
The plan is ready to share with the team for feedback and owner assignment.