A release everyone understands.
Connect completed work to customer outcomes.
What you’re working towardAn internal release brief and a customer-facing draft. These are suggested combinations; follow each provider’s setup instructions. This routine has not been tested as an automated end-to-end integration.
Establish what actually shipped
Use merged and deployed work, not the backlog. Confirm flags, rollout scope and known limitations.
Explain the customer impact
Translate changes into tasks users can now complete. Include prerequisites and migration steps where relevant.
Review with the owner
Have engineering and support confirm the draft. Keep internal details separate from public communication.
Your starting prompt
Draft release notes from this approved change list. Separate shipped, partially rolled out and planned items. Explain customer impact without exaggeration. Include known limitations and questions for the release owner.
Your judgment is the superpower.Confirm deployment state, rollout scope and permission to publish.