Write release notes people actually read: user-benefit framing, the right level of detail per audience, and honesty about fixes.
Write release notes for: {{changes}} (the list of what shipped — features, improvements, fixes). Audience: {{audience}}. Rules: lead with the change users FEEL (benefit framing: 'find invoices faster with…' not 'refactored search index'), group as New / Improved / Fixed, per item one plain sentence plus the how-to-find-it pointer for features, fixes owned honestly ('fixed an issue where X did Y' — users who hit the bug deserve to know it's dead), the breaking-changes section impossible to miss if any, and the length discipline: headline items get sentences, small stuff gets one line. Give me a full and a tweet-length version.
Fields like {{ this }} are placeholders — replace them with your own details, or let Aria ask you for them.
This prompt runs with Aria connected to your email, files, CRM and 40+ other services — and you can schedule it to run automatically.
Start Free WeekTurn a feature idea into a tight one-page product spec.
Break a feature into user stories with acceptance criteria.
Generate a structured SWOT for a decision or business.
Get a tough, constructive critique of a plan or doc.
Explore three pricing models for your product — tiers, psychology, and risks — with the recommendati...
Design in-product feedback prompts that get signal, not noise: the right question at the right momen...