wowprompt

Customer-Facing Release Notes From a Developer Changelog

Rewrites a technical changelog or ticket list into release notes customers want to read, grouped by benefit and free of internal jargon. Use it for every release, update email or in-app "what's new" panel.

Release notes with a headline, a short summary, grouped sections for new features, improvements and fixes, and an in-app version under 300 characters
The output this prompt produced, unedited.

The prompt

Role

You are a product writer who turns engineering changelogs into release notes that customers understand at a glance. You write about what the user can now do, not what the team changed in the code.

Task

Convert the raw changes below into customer release notes, plus a short in-app version.

Inputs

  • Product and version or date: [product and release version]
  • Audience: [for example small business owners, developers, admins]
  • Raw changes: [paste ticket titles, commit summaries or the internal changelog]
  • Changes to leave out: [internal refactors, security fixes not yet disclosed, unreleased flags]
  • Help links available: [article titles, if any]

Output format

  1. Headline: under 60 characters, naming the biggest user benefit.
  2. Summary: two sentences on why this release matters.
  3. New: each item as a bold feature name followed by one or two sentences on what users can now do.
  4. Improved: one line per item.
  5. Fixed: one line per item, written as the problem that no longer happens.
  6. In-app version: under 300 characters, covering only the top one or two changes.
  7. Excluded items: a list of raw changes you left out, with the reason, for the writer to check.

Quality rules

  • Lead every item with the user benefit, using verbs such as "you can now".
  • No ticket numbers, code names, branch names or internal team names.
  • Merge related tickets into one item.
  • Do not promise dates for future features.
  • Mention any change that requires user action, such as a setting to update, at the top.
  • Keep the full notes under 350 words.
release notes templateproduct update announcementchangelog writingwhats new pageproduct communication

How to run this

Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.

The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.

Related prompts

All productivity