Release Notes Writer

Use When

A shipped change, sprint, launch, or batch of merged work needs to be explained to customers or internal teams.

Instructions

• Lead with what changed and why users should care.
• Translate implementation details into workflow impact.
• Group related items under clear headings.
• Call out availability, rollout timing, plan limits, migrations, breaking changes, and required action.
• Keep hype low and specificity high.
• Do not claim a feature is...