Release Notes

Description

This prompt is designed to help product managers, developers, and marketing teams create clear and engaging release notes. By breaking down the structure into essential components, it ensures that key updates, improvements, and bug fixes are communicated effectively to the target audience. With a focus on user benefits and concise language, this prompt enables the creation of release notes that are both professional and compelling, driving user engagement and excitement for new features or improvements.

You are a product communications specialist. Help me create release notes for [Enter product/feature name] tailored to [Enter target audience: Users/Developers/Internal Team].

## Required Inputs
1. **Purpose of the Update:** Why this release matters and what problem it solves
2. **Key Changes:** For each major update, provide:
   - Feature name
   - What it does
   - Why it matters to the user
3. **Bug Fixes (optional):** Notable issues resolved
4. **Technical Updates (optional):** Changes relevant to developers

## Change Classification

Categorize every change into one of these types before writing:

| Category | Icon | Description | Example |
|----------|------|-------------|---------|
| New | :sparkles: | Brand-new capability | "New dashboard analytics view" |
| Improved | :arrow_up: | Enhancement to existing feature | "Faster search with autocomplete" |
| Fixed | :wrench: | Bug fix or issue resolution | "Fixed CSV export timeout on large datasets" |
| Deprecated | :warning: | Feature being phased out | "Legacy API v1 endpoints sunset in 90 days" |
| Breaking | :rotating_light: | Requires user action | "Authentication flow now requires OAuth 2.0" |

## Output Structure

### Release Header
- **Version:** [X.Y.Z]
- **Date:** [Release date]
- **One-line summary:** Lead with the biggest user benefit, not the feature name

### :sparkles: New
For each new feature:
- **Feature Name** — One-sentence description of what it does
- **Why it matters:** The user benefit in their language (not engineering jargon)
- **How to try it:** One-line instruction to access the feature

### :arrow_up: Improved
- Bullet list of enhancements to existing features (performance, usability, design)
- Include measurable impact where available (e.g., "30% faster load time")

### :wrench: Fixed
- Concise list, framed positively: "Fixed an issue where..." not "Bug: X was broken"
- Acknowledge user feedback where applicable: "Thanks to your reports, we fixed..."

### :warning: Deprecated (if applicable)
- What is being removed and when
- Migration path or alternative

### :rotating_light: Breaking Changes (if applicable)
- What changed and what action users must take
- Link to migration guide

### What's Next (1-2 sentences)
- Tease the next release or roadmap direction without over-promising

### Call-to-Action
- One clear next step: "Update now to experience [specific benefit]!"

## Tone Guidelines

| Audience | Tone | Focus | Jargon Level |
|----------|------|-------|-------------|
| Users | Conversational, benefit-focused | What they can do now | None |
| Developers | Technical, precise | API changes, migration notes | Full technical |
| Internal Team | Context-rich, strategic | Metrics impact, rollout plan | Business + technical |

Customize This Prompt