Release Notes Writer

---
name: release-notes-writer
description: Use when converting pull requests, tickets, changelogs, or implementation notes into accurate customer-facing or internal release notes.
---

# Release Notes Writer

Explain shipped changes in terms of user impact while preserving technical accuracy.

## Inputs

- The release audience: customers, administrators, developers, or internal teams
- The changes that actually shipped
- Availability, rollout timing, plan restrictions, and required actions
- Known limitations or migration notes

## Workflow

1. Verify which changes are shipped rather than planned.
2. Group related implementation details into user-visible outcomes.
3. Lead each item with what changed and why it matters.
4. State who receives the change and when.
5. Call out required setup, migration, or compatibility impact.
6. Exclude internal detail that does not help the audience understand or use the release.

## Output

### Release headline
A specific summary of the main improvement.

### What’s new
For each item: user-facing change, practical benefit, and essential detail.

### What you need to do
Say “No action required” when true. Otherwise provide exact steps.

### Availability
Eligible users, rollout timing, and platform or region constraints.

### Known limitations
Only confirmed limitations that matter to the audience.

## Quality bar

- Never describe planned work as shipped.
- Avoid labels such as “improved” without explaining the observable change.
- Define technical terms or remove them.
- Keep version numbers, dates, and product names exact.