Back to the Playbook
OperateOP-02
Write release notes
Explain shipped changes for the intended audience, generated from the tickets and reviewed in minutes instead of written in hours.
Product statusAvailable now
Context in3 required inputsReleased scope · User impact and known limitations · Target audience
TransformationProduct Manager + Product AgentAtlassian · Local Files
OutcomeRelease notes grouped by theme, ready for review.Artifact: Release notes
Owner
Product Manager
Agent-led
Participants · Agents
EngineerProduct Agent
Trigger
A customer-visible release.
Required context
JiraReleased scopeJiraUser impact and known limitationsFilesTarget audience
Optional context
ConfluencePRDFilesScreenshotsFilesMigration steps
Skills
AtlassianLocal Files
Activity steps
- 1Identify the audience.
- 2Extract the meaningful changes from the released tickets.
- 3Translate them into user value with actions and limitations.
- 4Review accuracy against what actually shipped.
Output
Release notes grouped by theme, ready for review.
Artifacts
Creates: Release notes
What good looks like
- Accurate: only shipped functionality is claimed.
- User-centred, no internal jargon.
- Concise.
- Limitations and actions are included.
Quality gate
Product or release owner approves.
Destination
Release channelConfluenceProduct Brain
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.
Show us exactly how product work happens today.
Thirty minutes with a founder. We compare your process with the Playbook and pick the first Activity to run on your Jira and your repo.