launch-announcer

Files (1)

• SKILL.md

SKILL.md (first lines)

# launch

You are an expert helping a Product Manager create product launch announcements that drive awareness, adoption, and excitement.

## File Location and Naming

**Location**: `nimbalyst-local/Marketing/Launches/[feature-name]-launch.md`

**Naming conventions**:
- Use kebab-case: `dark-mode-launch.md`, `api-v2-launch.md`
- Include "-launch" suffix for clarity
- For release notes: `nimbalyst-local/Marketing/Release-Notes/v[version]-release-notes.md`

## Announcement Templates

### 1. Internal Launch Announcement

```markdown
Subject: Launching [Feature Name] - [Date]

Team,

I'm excited to announce that [Feature Name] launches [Date]! This has been a [timeframe] effort and represents a significant milestone for [why it matters].

**What's Launching**:
[Brief description of feature and key capabilities]

**Why This Matters**:
- [Business impact 1]
- [User value 2]
- [Strategic importance 3]

**What to Expect**:
- [Rollout plan: phased/full launch]
- [How users will discover it]
- [Support resources available]

**Your Role**:
- Sales: [How to position this]
- Support: [Common questions, where to escalate]
- Engineering: [Monitoring plan, on-call rotation]

**Where to Learn More**:
- [Link to documentation]
- [Link to demo video]
- [Slack channel for questions]

Thank you to everyone who contributed: [shout-outs]

Let's make this launch successful!

[Your Name]
```

### 2. External Customer Announcement

```markdown
Subject: Introducing [Feature Name]

Hi [Customer Name],

We're excited to share something we've been working on: [Feature Name].

**What It Does**:
[One-sentence value proposition]

[Feature Name] helps you [solve specific problem] by [how it works]. Our customers told us they struggled with [pain point], and we built this to make [outcome] easier.

**Key Capabilities**:
- [Capability 1]: [Benefit]
- [Capability 2]: [Benefit]
- [Capability 3]: [Benefit]

**Getting Started**:
[Link to getting started guide]
[Link to video demo]

**Questions?**
Reply to this email or visit [support link].

We'd love to hear what you think!

Best,
[Your Name]
[Title]
```

### 3. Release Notes

```markdown
# Release Notes - [Version] - [Date]

## What's New

### [Feature Name]
**What**: [Brief description]
**Why**: [User benefit]
**How**: [Instructions to access]

## Improvements
- [Enhancement 1]
- [Enhancement 2]

## Bug Fixes
- Fixed: [Issue description]
- Resolved: [Issue description]

## Known Issues
- [Issue 1]: [Workaround if available]

## Coming Soon
- [Preview of next release]
```

## Best Practices

1. **Lead with Benefits**: "Save 2 hours per week" beats "Automated reporting"
2. **Tailor to Audience**:
  - Internal: Include logistics and team roles

From nimbalyst/skills, MIT.

More from nimbalyst/skills