Use this skill when the user asks to "write a launch announcement", "announce this feature", "write a launch email", "product announcement", "release notes", "launch blog post", "feature announcement to customers", "write the Slack announcement for this launch", or is preparing to communicate a new feature or product to users, customers, or the public.
You are writing launch communications — the external-facing message that converts a shipped feature into user awareness, adoption, and delight. Every launch announcement is a marketing and retention opportunity.
Frameworks: April Dunford (positioning clarity), Lenny's PRD guide (problem-oriented framing), copywriting principles (benefits over features).
Read memory/user-profile.md for: product name, stage, primary persona, current roadmap (to understand what just shipped), and stakeholder communication preferences. Read context/product/personas.md for tone calibration.
The #1 launch communication mistake: announcing a feature instead of announcing a solution.
Every announcement should:
Different channels need different formats:
In-app notification: 1–2 sentences. CTA button. No context needed. Email announcement: Subject line + 3–4 short paragraphs. Problem → Solution → How to access → CTA. Slack/Discord message: Conversational tone. Brief. Include a visual or GIF if possible. Blog post / changelog: Full narrative. 300–600 words. Problem, solution, how it works, what's next. LinkedIn post: Conversational, first-person. Story-forward. Include a real example or quote. Product Hunt post: Tagline + body. Includes what problem it solves, who it's for, and how to try it.
Ask which format(s) the user needs.
For each format requested, write:
Subject/headline: The benefit, not the feature name. "Now you can [do X] without [pain Y]"
Opening: Acknowledge the user's struggle or the request. Show you've been listening.
What's new: Describe the feature in user terms. What does the user do? What happens? What outcome do they get?
Why it matters: One sentence connecting the feature to user impact.
How to access: Clear, specific instructions. Don't assume they'll find it.
What's next: Optional. If there's more coming in this area, hint at it — creates anticipation.
CTA: One clear action: "Try it now", "See it in action", "Give us feedback".
Calibrate tone based on:
Produce: