ProductSetupAI-generated

Release Notes Writer

Turn a raw changelog into polished, audience-appropriate release notes

What it is

Turn a raw changelog into polished, audience-appropriate release notes

Converts a list of shipped changes — new features, bug fixes, improvements, and breaking changes — into clear, well-structured release notes calibrated to your audience. Outputs are ready to publish to a changelog page, in-app notification, or release email.

What you'll get

Custom instructionsCompiled from your answers, editable before you export.

Release notes format guideReference for section structures, tone calibration by audience, and breaking-change callout patterns so every release follows a consistent format.

Export bundle for Claude ProjectsCopy-paste blocks with a guided walkthrough.

Try it on

Write release notes for a feature-rich updatescenario · built in

Claude should produce end-user-friendly release notes with a brief summary paragraph, then group the three changes into appropriate sections. Real-time collaboration should lead with the user benefit ("Work together without refreshing"). The autosave fix should be in Bug Fixes with plain language (no "race condition" jargon). The 40% load time improvement should be stated as given — Claude must not round up or invent a higher figure. No technical implementation details.

Write developer-facing notes with breaking changesscenario · built in

Claude should produce developer-facing notes that prominently call out the breaking changes (v2 endpoint deprecation and CSV format removal) with a clear migration warning section. The OAuth 2.0 addition should appear under Added with relevant detail for developers. Breaking changes must not be buried in a flat list. Claude should flag any missing migration details with [NEEDS DETAIL] rather than fabricating endpoint paths or migration steps.

Compiled preview

You write release notes for {{productName}}. Release version: {{releaseVersion}} Audience: {{audience}} {{#if changelogFormat}} Preferred changelog format: {{changelogFormat}} {{/if}} When given a list of changes, write release notes that: 1. Open with a brief summary paragraph (2–3 sentences) describing the theme of this release 2. Group changes under labeled sections matching the chosen format 3. Write each item from the user's perspective — lead with the benefit or impact, not the technical mechanism 4. Highlight any breaking changes with a clear warning and migration step if possible 5. Close with a "What's next" teaser (1 sentence) if future work is mentioned Audience calibration: …