Is Release Notes Drafter free?

The setup guide and prompt are free. In Claude it works on any plan, including Free, which allows up to five projects. In ChatGPT it needs Work on the web, which comes with Plus, Pro, Business, Enterprise or Edu.

Does it publish the release notes?

No. It labels the result Draft for writer and product-owner review. A person checks the wording and publishes it, and it never claims the release happened.

What if a ticket is vague?

It holds the ticket and asks a precise question instead of guessing. A ticket that only says improve export gets a question about what changed, not an invented benefit.

Does it read my ticket tracker?

No. You paste the ticket extracts, or in Claude attach a CSV export of them. It never queries a tracker, inspects code or edits documentation.

Can my product owner use the same setup?

In Claude, on a Team or Enterprise plan, you can share the project with Can view, so the product owner works from the same instructions and files. Each person’s chats stay private unless shared.

Release Notes Drafter

Draft release notes from confirmed changes

Release Notes Drafter is an AI agent you set up in the ChatGPT or Claude you already use. Give it the ticket extracts for one release and your approved product names, and it drafts customer release notes from the confirmed changes only, with held items, exclusions and questions for the product owner kept apart.

Pick your AI for the steps and the prompt

About each AI:ChatGPT WorkClaude app

Checked 29 Oct 2026. Not run by JuicyAgents yet. Written from each AI’s official docs; the example is illustrative.

Release Notes Drafter · reply in the chat

1 change drafted, 2 excluded, 1 held

OrdersExport CSV now includes the Order reference columnDraft
T2 and T3An internal update and a planned feature, each with a reasonExcluded
T4Waits for availability, the portal name and the measured effectHeld
SpeedNo speed improvement is claimed

Illustrative example: four fictional tickets for release R-8 of a made-up product, Cedar Desk

How it works

What it does for you, and what it leaves to you.

Technical writers assemble customer release notes from inconsistent tickets and product-manager input. Missing context and invented product names can make generated drafts costly to review.

Interpret mixed ticket notes and create a checkable first draft. Practitioners disagree about AI time savings; this exact procedure has not been measured. A customer-facing release-note field, a release filter and a fixed template can reduce drafting work. Good ticket hygiene and product-owner approval matter more than another tool. Use a manual draft when the packet is small or missing reliable change details.

You stay in charge. The product owner confirms production availability and customer impact. The writer checks wording, confidential details and source references before a person publishes anything.

You get

A customer release-note draft plus excluded items and owner questions

It never

Publish anything or claim the release happened
Include a change that isn’t confirmed in production
Invent screen names, settings, steps or performance gains
Browse, query your tracker or inspect code
Put ticket references or security details in customer copy

The draft it writes

The example above, in words.

The draft has one bullet under Orders: “Export CSV now includes the Order reference column.” T1 is cited in the internal review section, not in customer copy. T2, an internal dependency update, and T3, saved filters that are only planned, are excluded with reasons. T4 is held with questions about availability, the portal name and the measured effect, and no speed improvement is claimed.

Settings

The setup prompt starts with the defaults, marked here.

Draft structure

Choose how the assistant organizes the result; evidence and review rules stay the same.

By customer task (default)
By change type

Your working rules

Preferred headings and approved terminology. Include only material your organization permits you to share.

Optional. Empty unless you fill it in.

Check the first result

Each setup page has a fictional exercise to paste first. A good answer to it meets all of these.

Only T1 enters the customer-facing draft.
Cedar Desk, Orders and Export CSV keep the approved names.
Internal source mapping and unanswered questions stay separate from customer copy.
Removing an essential input causes a question or a blocked item, not an invented fact.
Changing the setting changes the requested output while source references and fixed limits remain.

Questions people ask

Is Release Notes Drafter free?: The setup guide and prompt are free. In Claude it works on any plan, including Free, which allows up to five projects. In ChatGPT it needs Work on the web, which comes with Plus, Pro, Business, Enterprise or Edu.
Does it publish the release notes?: No. It labels the result Draft for writer and product-owner review. A person checks the wording and publishes it, and it never claims the release happened.
What if a ticket is vague?: It holds the ticket and asks a precise question instead of guessing. A ticket that only says improve export gets a question about what changed, not an invented benefit.
Does it read my ticket tracker?: No. You paste the ticket extracts, or in Claude attach a CSV export of them. It never queries a tracker, inspects code or edits documentation.
Can my product owner use the same setup?: In Claude, on a Team or Enterprise plan, you can share the project with Can view, so the product owner works from the same instructions and files. Each person’s chats stay private unless shared.

Have us set it up

Rather not set it up yourself?

We set up Release Notes Drafter in your own accounts and the AI you already pay for, test it on your real work, and hand it over with a short walkthrough.

From $299

Runs in your accounts; you own everything
Tested before handover
Money back if we can’t make it work

Request a setup