Strawberry

AI can assemble release notes from the work that actually shipped.

It can read the tickets, pull requests, test notes, and product decisions you point it to, then prepare audience-specific release notes for review. The release owner still decides what is ready to announce and what needs a more careful explanation.

Release notes are a translation job, not a ticket export.

“Refactor entitlement service” may be accurate internally and useless to the person deciding whether their workflow changed. The reader needs to know what they can now do, what they need to change, and whether a known limitation remains.

Strawberry can gather the release inputs you select and draft a plain-language account of the visible impact. It should preserve links to the source issue or PR so the owner can check that a polished sentence did not overstate the work.

One deployment can need three different explanations.

Support may need workarounds, sales may need an accurate customer benefit, and engineering may need the implementation record. A single all-purpose changelog usually becomes too vague for one group and too technical for another.

An agent can prepare separate drafts from the same approved source set: a customer update, an internal support brief, and a concise launch note for the team. The release lead reviews the claims before any of those drafts become published text.

The missing information should be visible before launch day.

Release-note work often stalls because no one knows whether a feature flag is on, migration guidance exists, or the final copy has been approved. Hiding those gaps in a draft produces a confident document with missing operational detail.

Strawberry can compare the required release-note fields with the evidence it finds and return an explicit missing-information list. That lets the owner ask for the screenshot, rollout date, or support guidance before the change reaches customers.

Publication should remain a deliberate release decision.

A release note can trigger customer questions, change a sales conversation, or reveal a rollout that is not complete. Writing the draft is safe preparation; publishing it is a communication decision.

Save the release-evidence checklist as a product-note skill and use it after each planned deployment. Require approval for publishing, posting, or sending the finished note so the accountable owner sees the exact wording and destination.

Experience Strawberry for free

Download

Trusted by fast-growing companies worldwide

Frequently asked questions

It can use the tickets and other release evidence you provide to prepare a draft. Verify that the note reflects what actually shipped rather than the original plan.

Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents