Choose one of three approaches. The steps for that option appear below.
Choose an option above. On a phone, swipe the tabs left or right to see all options →
One Claude chat groups the titles, drafts plain notes and flags claims to confirm. You check and decide.
Gather titles
Group, draft, flag
Check and decide
Use: You
Have ready: the merged PR titles and linked ticket summaries.
Check every title has its ticket summary.
Use: Claude
In one chat, ask for grouping by user impact with a held-back list, plain wording citing tickets, then flags on lines an engineer must confirm.
What to paste into the tool
Task: Proposed grouping: grouped list plus held-back list. Here are merged PR titles with ticket summaries for version 2.4. Group them by user impact as new, improved, fixed. Put internal-only items on a separate held list with the reason. Every line keeps its ticket ID. Describe nothing that is not in the tickets. Task: Release notes draft. Rewrite each proposed group as release notes in plain user language. Each line ends with its ticket ID. Say nothing that is not in the ticket text. This is a draft for approval, not for publishing. Task: Confirmation list. Read the draft against the ticket text. Add an inline [confirm] marker on every line that asserts behaviour, scope or effect an engineer should verify, and list those claims separately.
Use: You
Check the notes and the confirmation list against your tickets. Approve the notes or hold them and list the fixes.
Check grouping and held items. Check each line against the ticket text and each flagged claim against what shipped. Approve the notes only when every line matches your tickets; otherwise hold the draft and list the fixes. Nothing is published: the draft stays in the chat until the product owner releases it.
Notion AI drafts the notes page from your tickets. You correct it; an engineer checks each flagged claim.
Gather tickets
Draft notes page
Check and correct
Mark claims
Engineer checks claims
Approve or hold
Use: You
Have ready: the release tickets in the workspace.
Check the tickets are the ones for this release.
Use: Notion AI
Ask Notion AI to draft the notes page from the tickets: grouped by user impact, ticket ID per line, internal-only items on a held-back list.
What to paste into the tool
Task: Release notes draft grouped by user impact; Held-back list with reasons. Draft the version 2.4 release notes page from the tickets in this workspace in one pass. Group lines by user impact: new, improved, fixed. Put internal-only items on a separate held-back list with the reason. Every line ends with its ticket ID. Describe nothing beyond the ticket pages. Mark the page clearly as a draft for product-owner approval, not for publishing.
Use: You
Check the draft page against what shipped: correct the grouping and held-back list and edit the wording.
Check the grouping and held-back list before anything is treated as approved. Check claims match what shipped.
Use: Notion AI
Ask Notion AI to mark claims in the draft that need engineering confirmation against the ticket pages.
What to paste into the tool
Task: Confirmation list. Compare the draft page with the ticket pages. Add [confirm] markers on every line asserting behaviour, scope or effect an engineer should verify, and list those claims on the page.
Use: The engineer
Check the confirmation list against the draft and the tickets, then correct each claim that is wrong.
Use: You
Approve the release notes page, or hold it and list the fixes.
Approve only when every line matches the tickets; nothing is published by this path.
ChatGPT proposes the grouping, then drafts plain notes from your approved version. An engineer checks claims.
Gather inputs
Propose grouping
Approve grouping
Draft plain wording
Engineer checks claims
Approve or hold
Use: You
Have ready: the merged PR titles and ticket summaries.
Check the ticket summaries are the authorised source and are current.
Use: ChatGPT
Paste the titles and summaries into ChatGPT and ask for a grouping (new, improved, fixed) plus a held list with reasons.
What to paste into the tool
Task: Release notes grouping. Here are the merged change titles with ticket summaries. Propose a grouping as new, improved or fixed, with each item citing its ticket ID. Put internal-only items on a held list with the reason. Cover every merged item once, or list it as omitted with the reason. Say nothing that is not in the ticket text. Proposal for approval, not for publishing.
Use: You
Check the grouping against the tickets, correct placements, and approve the grouping and the held list.
Check each item's placement and held reason against its ticket summary. The grouping and held list are your call.
Use: ChatGPT
Paste your approved grouping and the ticket summaries into ChatGPT and ask for a plain-language draft citing tickets.
What to paste into the tool
Task: Release notes draft. Here is my approved grouping of merged changes with ticket summaries. Rewrite each group as release notes in plain user language. Each line ends with its ticket ID. Say nothing that is not in the ticket text. Draft for approval, not for publishing.
Use: The engineer
Check the draft against the tickets, list every claim that needs your confirmation, then correct any that are wrong.
Use: You
Approve the release notes, or hold them and list the fixes.
Approve only when every line matches the tickets; otherwise hold the draft and list the fixes. Nothing is published by this path.
Best when: Ticket text is short enough to paste and one place suits you
What it does: Claude groups, drafts and flags; you check and decide
Strong at: Drafts and edits text in many formats
Limit: Usage capped in 5-hour and weekly windows
Free plan: Yes
Best when: Your release tickets are already tracked in Notion
What it does: Notion AI drafts and flags; you and an engineer check
Strong at: Drafts, edits and translates content
Limit: Agent needs Business plan, monthly credits per member (as of October 28, 2026)
Free plan: Paid plan needed
Best when: You want to approve the grouping before any wording
What it does: ChatGPT groups and drafts; you approve; engineer checks
Strong at: Writes, rewrites and summarises text
Limit: Free plan limits file uploads, image generation, voice and data analysis
Free plan: Yes
Before you paste into any AI tool, remove any confidential information. Put it back at the end.
Deciding between ChatGPT and Claude for this? See the comparison.
Every merged item is included, merged into another line, or listed as omitted with the reason.
Each line cites its ticket and describes nothing that is not in the tickets.
The product owner approves the wording and checks claims against what shipped; an engineer confirms or corrects each flagged claim.
Do not publish: in every path the product owner releases the notes.
Check the result against your original inputs. Approve it before sharing or acting.