Generate Feature Announcement Content

This prompt generates feature announcement copy designed to excite users and drive adoption. It takes structured input about the feature (name, description, user benefit, availability tier) and its context (whether it was a customer request, the problem it solves, expected use cases, and release type), then produces six deliverables in one pass: an email announcement, a short in-app notification, a blog post outline, social media posts for Twitter and LinkedIn, a product changelog entry, and a help doc introduction.

Create feature announcement content for:

**Feature:**
- Name: [Feature name]
- Description: [What it does]
- User Benefit: [Why it matters]
- Availability: [All users/Plan tier/Beta]

**Context:**
- Customer Request: [Was this requested?]
- Problem Solved: [What pain point]
- Use Cases: [How customers will use it]
- Release Type: [Major/Minor/Update]

Generate:
1. Email announcement
2. In-app notification (short)
3. Blog post outline
4. Social media posts (Twitter, LinkedIn)
5. Product changelog entry
6. Help doc introduction

It applies two announcement frameworks: AIDA (Attention - what's new, Interest - why it matters, Desire - specific benefits and use cases, Action - how to try it) and Problem-Solution-Result ("You asked for better X" / "Today we're launching Feature" / "Now you can outcome"). Each output format has its own template: the email leads with a customer-pain-point hook and a bulleted "What You Can Do" list before a getting-started link; the changelog entry is a terse one-liner plus brief use-case elaboration and a docs link; the social posts are written to platform norms - short and benefit-led for Twitter, framed as a customer-driven win with a checklist of benefits for LinkedIn.

Use it when shipping a feature that needs coordinated announcement copy across multiple channels at once, especially when you want every channel's message to trace back to the same customer pain point and benefit framing rather than being written independently. It's built around a customer-request/problem-solved narrative, so it fits best when there's a genuine pain point or requested capability behind the release - a purely internal or cosmetic change won't have much to plug into the "You asked for better X" framing.

Input is the feature's name, description, user benefit, availability, and release context (customer request status, problem solved, use cases, release type). Output is six coordinated pieces of announcement copy: email, in-app notification, blog outline, Twitter and LinkedIn posts, changelog entry, and help doc intro - all built from the same input so the framing stays consistent across channels.

Product marketers, PMs, and growth teams who need consistent, multi-channel feature announcement copy generated from one set of inputs instead of writing each channel's version from scratch.