Customer-Facing Release Notes

Prompt template

Turn this engineering changelog into customer-facing release notes:

{{raw_changelog}}

Rules:
- Skip anything purely internal (refactors, dev-only tooling, dependency bumps).
- Group by user impact, not by codebase: New, Improved, Fixed.
- Each bullet is one sentence, present tense, written from the user's perspective ('You can now…', 'Faster…', 'Fixed an issue where…').
- No emoji. No version numbers. No GitHub PR links.
- Tone: friendly, factual, lowercase headers if any.
- If a change is interesting but small, give it one bullet — don't pad.

Audience: {{audience}}.
Length: 6–12 bullets total.

Curator notes

The 'skip purely internal' rule kills the temptation to dump the engineering log. The 'don't pad' line stops the model from inventing improvements that didn't happen.