Release Notes

Release notes turn shipped work into a clear narrative for customers, stakeholders, or internal teams.

Release notes are generated from shipped work in a selected period. For how connected activity becomes completed work, see Captured Work.

What release notes contain

Release notes are editable summaries of what shipped in a selected period.

Audiences can be internal, external, or executive. Edit the generated content before sharing so the note matches the audience and emphasizes outcomes for readers who do not need implementation detail.

Sharing

You can copy release note content as Markdown or send it to another tool. The format is useful for Slack, docs sites, email, changelogs, and stakeholder updates.

Generate separate release notes for separate audiences when the same shipped work needs different framing:

Audience	Emphasize
External	User-facing changes, improvements, and product value without internal implementation detail.
Internal	Implementation notes, resolved blockers, decisions, and next steps.
Executive	Outcomes, risk, customer impact, and strategic progress.

Source material

Good release notes depend on completed work, pull requests, taxonomy, and comments that explain what changed and why.

Private work is excluded. If important shipped work is private, add enough team-visible context before generating the note.

Move into Stakeholder Updates when release notes need to become a broader status narrative.