To run this task you must have the following required information:

> Launch name, key messages, launch date, stakeholder groups to communicate with

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 stakeholder roles and communication timing)

2. Gather communication context:
- What's the launch? (Brief description)
- What are the 2-3 key messages?
- When is launch day?
- Which stakeholders need communication?
  - Executive team
  - Sales team
  - Support team
  - Broader company
  - Partners (if applicable)

Different stakeholders need different information and framing.


3. Generate Executive Briefing (T-2 weeks):

```markdown
## Executive Briefing: [Launch Name]

**Date:** [Date]
**Launch Date:** [Date]

### What We're Launching
[2-3 sentences]

### Why It Matters
- **Customer Impact:** [What problem it solves]
- **Business Impact:** [Revenue, retention, competitive positioning]
- **Strategic Alignment:** [How it fits company strategy]

### Key Messages
1. [Primary message for external use]
2. [Secondary message]

### Potential Questions
- **Q: [Anticipated question]**
  A: [Talking point]
- **Q: [Anticipated question]**
  A: [Talking point]

### Your Role
- [Any executive actions needed]
- [Events/calls they should join]

### Timeline
[Key milestones between now and launch]
```


4. Generate Sales Team Briefing (T-1 week):

```markdown
## Sales Enablement: [Launch Name]

**Live Date:** [Date]

### The Pitch (30 seconds)
[Elevator pitch version for sales calls]

### What's New
- [Feature/capability 1]
- [Feature/capability 2]
- [Feature/capability 3]

### Who Cares
**Ideal for:** [Persona/segment most likely to care]
**Best use cases:** [Specific scenarios]

### Talk Track
"When talking to [persona], lead with [benefit]. The key differentiator is [X].
Common objection: [objection] — respond with [counter]."

### What's NOT Included
[Set expectations on scope/limitations]

### Pricing/Packaging
[Any changes or how this fits existing tiers]

### Resources
- Demo: [Link]
- Battlecard: [Link]
- FAQ: [Link]

### Questions?
Reach out to [owner] in [channel]
```


5. Generate Support Team Briefing (T-1 week):

```markdown
## Support Briefing: [Launch Name]

**Live Date:** [Date]

### What's Changing
[Clear description of what customers will see/experience]

### Common Questions (Predicted)
- **Q: [Question]**
  A: [Answer]
- **Q: [Question]**
  A: [Answer]

### Known Limitations
- [Limitation 1 and workaround if any]
- [Limitation 2 and workaround if any]

### Troubleshooting
**Issue:** [Common issue]
**Solution:** [Steps]

**Issue:** [Common issue]
**Solution:** [Steps]

### Escalation Path
- L1: [Standard support]
- L2: [Escalation criteria and contact]
- Engineering: [When to escalate and contact]

### Documentation
- Help article: [Link]
- Internal wiki: [Link]

### Questions Before Launch?
Ask in [channel] before [date]
```


6. Generate Company-Wide Announcement (Launch Day):

```markdown
## 🚀 [Launch Name] is Live!

Hey team,

Today we're launching [feature/product] — [one-line description].

### Why It Matters
[2-3 sentences on customer and business impact]

### The Quick Version
[What it does in plain language]

### How to Talk About It
If someone asks you about [launch], here's the key message:
"[Key message in quotable form]"

### Resources
- Blog post: [Link]
- Demo: [Link]
- FAQ: [Link]

### Shoutouts
Huge thanks to [teams/individuals] who made this happen!

Questions? Drop them in [channel].

[Sign-off]
```


7. Summarize all communications created:
- Executive briefing (send T-2 weeks)
- Sales enablement (send T-1 week)
- Support briefing (send T-1 week)
- Company announcement (send launch day)

Remind user to customize with actual links, names, and dates before sending.