Release Notes and Feature Announcement Articles
Explain changes in terms of customer benefit.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Rewrite release notes so they explain customer benefit. Product and audience: [PRODUCT_AND_AUDIENCE]. Raw change list (as engineers wrote it): [PASTE_CHANGE_LIST]. Release date and version: [RELEASE_DATE_AND_VERSION]. Known limitations: [LIMITATIONS]. Return: BEFORE: take five items from the raw list and show them as written with problems marked in brackets ([internal jargon], [no benefit], [missing who it affects], [unclear what changed]). AFTER: a polished release note with these parts: a headline that names the biggest customer benefit; a two-sentence summary; "What's new" items, each with a short title, what it lets you do, how to use it in one or two steps, and who it is for; "Improvements and fixes" as a short bulleted list in customer language; "What you need to do" (actions or changes required, such as updating a setting); "Known limitations"; and where to give feedback. VARIANTS: a 60-word in-app announcement, a 100-word email, and a one-sentence social post. CHECKS: a table of claims to verify with engineering before publishing. Do not exaggerate, and do not describe features that are not in the change list. Keep the tone friendly and concrete.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.