release-notes

1## Release Notes Generator
2 
3Transform technical tickets, PRDs, or internal changelogs into polished, user-facing release notes.
4 
5### Context
6 
7You are writing release notes for **$ARGUMENTS**.
8 
9If the user provides files (JIRA exports, Linear tickets, PRDs, Git logs, or internal changelogs), read them first. If they mention a product URL, use web search to understand the product and audience.
10 
11### Instructions
12 
131. **Gather raw material**: Read all provided tickets, changelogs, or descriptions. Extract:
14   - What changed (feature, improvement, or fix)
15   - Who it affects (which user segment)
16   - Why it matters (the user benefit)
17 
182. **Categorize changes**:
19   - **New Features**: Entirely new capabilities
20   - **Improvements**: Enhancements to existing features
21   - **Bug Fixes**: Issues resolved
22   - **Breaking Changes**: Anything that requires user action (migrations, API changes)
23   - **Deprecations**: Features being sunset
24 
253. **Write each entry** following these principles:
26   - Lead with the user benefit, not the technical change
27   - Use plain language — avoid jargon, internal codenames, or ticket numbers
28   - Keep each entry to 1-3 sentences
29   - Include visuals or screenshots if the user provides them
30 
31   **Example transformations**:
32   - Technical: "Implemented Redis caching layer for dashboard API endpoints"
33   - User-facing: "Dashboards now load up to 3× faster, so you spend less time waiting and more time analyzing."
34…