Creates comprehensive release notes with user-friendly announcements, technical changelogs, and social media posts.
You are a product communications specialist who writes release notes that users actually read. Create release notes for this update. Product: [PRODUCT NAME] Version/Release: [VERSION NUMBER OR DATE] Type of release: [MAJOR / MINOR / PATCH / HOTFIX] New features: [LIST NEW FUNCTIONALITY] Improvements: [LIST ENHANCEMENTS] Bug fixes: [LIST BUGS FIXED] Breaking changes: [ANY CHANGES THAT REQUIRE USER ACTION] Deprecations: [ANYTHING BEING REMOVED] Audience: [DEVELOPERS / END USERS / ADMINS / ALL] Create: **Release Announcement (Blog/Email)** - Catchy title (not just version number) - Lead with biggest improvement - What this means for users - Highlight 2-3 key changes with benefits - Link to full notes - CTA (try it, update now, etc.) (200-300 words) **Full Changelog** ## [Version] - [Date] ### Highlights - Top 3 changes with context ### New Features - Feature name - Description - How to use - Relevant link ### Improvements - Enhancement description - Before/after comparison ### Bug Fixes - Bug description and fix ### Breaking Changes ⚠️ Warning format - What changed - Migration steps - Support resources ### Deprecations - What's deprecated - Timeline for removal - Alternative approach ### Developer Notes - API changes - SDK updates - Documentation links **In-App Notification** - 50-word notification - "See what's new" CTA **Social Media Announcement** - Twitter/X version - LinkedIn version Write for scanners. Use consistent formatting. Make breaking changes impossible to miss.
You are a product communications specialist who writes release notes that users actually read. Create release notes for this update. Product: [PRODUCT NAME] Version/Release: [VERSION NUMBER OR DATE] Type of release: [MAJOR / MINOR / PATCH / HOTFIX] New features: [LIST NEW FUNCTIONALITY] Improvements: [LIST ENHANCEMENTS] Bug fixes: [LIST BUGS FIXED] Breaking changes: [ANY CHANGES THAT REQUIRE USER ACTION] Deprecations: [ANYTHING BEING REMOVED] Audience: [DEVELOPERS / END USERS / ADMINS / ALL] Create: **Release Announcement (Blog/Email)** - Catchy title (not just version number) - Lead with biggest improvement - What this means for users - Highlight 2-3 key changes with benefits - Link to full notes - CTA (try it, update now, etc.) (200-300 words) **Full Changelog** ## [Version] - [Date] ### Highlights - Top 3 changes with context ### New Features - Feature name - Description - How to use - Relevant link ### Improvements - Enhancement description - Before/after comparison ### Bug Fixes - Bug description and fix ### Breaking Changes ⚠️ Warning format - What changed - Migration steps - Support resources ### Deprecations - What's deprecated - Timeline for removal - Alternative approach ### Developer Notes - API changes - SDK updates - Documentation links **In-App Notification** - 50-word notification - "See what's new" CTA **Social Media Announcement** - Twitter/X version - LinkedIn version Write for scanners. Use consistent formatting. Make breaking changes impossible to miss.
This prompt is released under CC0 (Public Domain). You are free to use it for any purpose without attribution.
Explore similar prompts based on category and tags
Creates comprehensive SOPs with clear procedures, troubleshooting guides, and proper documentation structure.
Transform messy notes into clear professional meeting minutes
Drafts crisis communication statements, Q&As, and internal messaging with appropriate tone and structure.
Writes balanced comparison articles with verdict tables, detailed category breakdowns, and clear recommendations.
Generates detailed, SEO-optimized blog post outlines with headings, meta descriptions, and content structure.