Generate Feature Announcement Content
A prompt template that generates a full feature-launch content set - email, in-app notice, blog outline, social posts, and changelog - at once.
1.0.0Add to Favorites
Why it matters
Create compelling announcements for new features to drive user excitement and adoption across multiple communication channels.
Outcomes
What it gets done
Draft email announcements to inform users about new features.
Generate concise in-app notifications for immediate user awareness.
Outline blog posts to provide in-depth feature details.
Create social media posts for platforms like Twitter and LinkedIn.
Install
Add it to your toolbox
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/vb-feature-announcement | bash Overview
Feature Announcement Copy
A prompt template that generates a coordinated set of feature-launch content - email, in-app notification, blog outline, Twitter/LinkedIn posts, changelog entry, and help-doc intro - from one feature description. Use when a new feature, tier capability, or beta needs consistent launch copy across multiple channels at once. Not suited for no-news releases or non-copy launch strategy work.
What it does
This prompt template turns a single feature description into six pieces of launch content at once: an email announcement, a short in-app notification, a blog post outline, social media posts (Twitter and LinkedIn), a product changelog entry, and a help-doc introduction. The prompt asks for the feature's name, description, user benefit, and availability (all users, a specific plan tier, or beta), plus context - whether it was a customer request, what pain point it solves, expected use cases, and the release type (major/minor/update).
Two announcement frameworks structure the copy: AIDA (Attention - what's new; Interest - why it matters; Desire - specific benefits/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]").
The email template opens with a "New: [Feature] is here" subject line, acknowledges the pain point the user asked to have solved, states what's new and how it works, lists 2-3 concrete use cases as bullets, and closes with a getting-started link and an invitation to reply with questions. The social templates give each platform its own register - a short, punchy Twitter post leading with the benefit and a try-it link, and a longer LinkedIn post opening with the customer-requested framing, a short checklist of named benefits, and a specific use case before the availability note. The changelog entry format is deliberately terse: a dated header, an "Added:" line with a one-line description, a short capability statement, and a docs link.
When to use - and when NOT to
Use this whenever a new feature, plan-tier capability, or beta needs launch content across multiple channels at once - it's built to keep the messaging and benefit framing consistent across email, social, changelog, and docs rather than writing each channel's copy independently. It is not suited for announcements with nothing new to say (a pure bug-fix release) or launches that need channel-specific strategy beyond copy (paid promotion planning, influencer outreach).
Inputs and outputs
Inputs: the feature's name, description, user benefit, availability tier, whether it was customer-requested, the problem it solves, expected use cases, and release type. Outputs: an email announcement, an in-app notification, a blog post outline, Twitter and LinkedIn posts, a changelog entry, and a help-doc introduction - all sharing the same benefit framing.
Integrations
A standalone prompt template with no external tool dependencies.
Who it's for
Product marketers and PMs who need a consistent, multi-channel feature launch content set generated from one input, rather than writing email, social, and changelog copy separately from scratch each time.
Source README
Feature Announcement Copy
Write feature announcements that excite users and drive adoption.
Prompt Template
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
Announcement Frameworks
AIDA Structure
- Attention: What's new
- Interest: Why it matters to them
- Desire: Specific benefits/use cases
- Action: How to try it
Problem-Solution-Result
- "You asked for better [X]"
- "Today we're launching [Feature]"
- "Now you can [outcome]"
Email Announcement Template
Subject: "New: [Feature] is here"
"Hi [Name],
[Feature Name] is now available.
You told us you wanted a better way to [pain point]. We listened.
What's New:
[Feature] helps you [key benefit] by [how it works].
What You Can Do:
• [Use case 1]
• [Use case 2]
• [Use case 3]
Getting Started:
[Link to feature / Help doc]
Have questions? Reply to this email or check out our [help center link].
Happy [using it]!
[Team]"
Social Media Templates
Twitter:
"🎉 New feature alert!
[Feature Name] is here.
Now you can [key benefit] without [previous pain].
Try it now → [link]"
LinkedIn:
"Excited to announce [Feature Name]-the [Product] feature our customers have been asking for.
Here's what it does:
✓ [Benefit 1]
✓ [Benefit 2]
✓ [Benefit 3]
[How it helps + specific use case]
Available now to [all users / tier]. Link in comments."
FAQ
Common questions
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.