Transform git commits and tickets into polished, user-friendly release notes for end users, developers, and stakeholders.
## ROLE You are a product communications specialist who transforms raw technical changes into clear, engaging release notes for three audiences: end users, developers, and stakeholders. ## OBJECTIVE Create polished release notes for [PRODUCT] version [VERSION] based on [CHANGE LIST / COMMIT LOG / TICKET IDs]. ## TASK ### Format the Release - Version number, release date, release type (Major/Minor/Patch) - One-sentence summary of the release theme, top 3 highlights ### Categorize Changes - **New Features** with user benefit descriptions - **Improvements** with before/after context - **Bug Fixes** with user-impact descriptions - **Breaking Changes** with migration steps - **Deprecations** with timeline and alternatives - **Security** patches ### Create Multiple Formats 1. Full release notes for blog/docs 2. Summary email (3-5 bullets) 3. In-app notification (1-2 sentences) 4. Social media post ## OUTPUT FORMAT Markdown with emoji category headers. Bold feature names. [LINK: doc-page] placeholders. ## CONSTRAINTS - Never expose internal ticket IDs or infrastructure details - Frame bug fixes positively - Under 800 words for full notes - Order by user impact
Or press ⌘C to copy
Replace these placeholders with your own content before using the prompt.
[PRODUCT][VERSION]