Back to the Playbook
OperateOL-01
How to write release notes
Translate shipped changes into user value and never equate a merged change with general availability.
Product statusAvailable now
Input3 required inputsMerged changes in the release range · Resolved Jira issues and availability evidence · Initiative focus and approved Product Brain guidance
SkillsCollect and write release notes · Prepare task context · Review an artifact against agreed criteriaProduct Marketing + Product Marketeer Agent
OutcomeCustomer-facing release notes grouped by theme, an internal changelog with issue keys, and the list of untracked merged changes.Artifact: Release notes
Owner
Product Marketing
Human + Agent
Participants · Agents
Product ManagerEngineerProduct Marketeer Agent
Trigger
A release or a set of shipped changes is confirmed.
Required context
CodeMerged changes in the release rangeJiraResolved Jira issues and availability evidenceProduct BrainInitiative focus and approved Product Brain guidance
Optional context
ConfluenceUser-facing limitationsFilesLaunch plan and audiences
Skills
Collect and write release notesPrepare task contextReview an artifact against agreed criteria
Suggested conversation arc
- 1Verify what users can accessConfirm the actual release scope, audiences and availability restrictions; exclude unshipped work and uncertain fixes.Skills: Prepare task context
- 2Draft New, Improved and FixedWrite short entries describing what users can now do, organised only under applicable headings; remove internal names and unsupported performance claims.Skills: Collect and write release notes
- 3Review release accuracyCheck every entry against release facts, including limitations and affected audiences. Verify that fixed claims have evidence of resolution.Skills: Review an artifact against agreed criteria
- 4Confirm the final publication draftAgree the final text and intended release channel; publishing is a separate explicitly authorised action, not a consequence of completing this Activity.
Output
Customer-facing release notes grouped by theme, an internal changelog with issue keys, and the list of untracked merged changes.
Artifacts
Creates: Release notes
What good looks like
- Every entry traces to a merged change and its Jira issue.
- Merged never means generally available without availability evidence.
- Untracked changes are listed, never dropped or given an invented ticket.
Quality gate
A named person confirms the final text and channel; publishing stays a separate authorised action.
Destination
Release channelConfluence
Usually next
People and agents work from the same Product Brain. The owner stays accountable. Assigned agents prepare and check. A named person approves at the gate.
Deep dives from the AI PM Lab
Articles that explain the thinking behind this Activity.
Choose the path that matches your role.
Set the Product AI direction with us, or test the shared Product Brain on real work with Jira and code.