Release Notes — Customer-Facing

Prompt template

Write the customer-facing release notes for {{product}} v{{version}}.

Engineering changelog:
{{changelog}}

Audience: {{audience}}

Output structure:
1. A one-sentence opener that says the most useful new thing in plain language.
2. A 'WHAT'S NEW' section: 2-4 bullets, each in the format 'You can now <verb> <object>.' Each bullet < 18 words.
3. A 'WHAT WE FIXED' section: 1-3 bullets phrased as the user's frustration, not the engineering cause ('uploads no longer time out on slow networks', not 'increased S3 retry timeout to 30s').
4. A closing line linking to the docs.

Rules: no 'we are excited', no 'under-the-hood improvements', no version-number trivia.

Curator notes

The 'phrased as the user's frustration' rule for fixes is the difference between release notes that get read and ones that get skipped. Worth the verbosity.