How to write end-of-sprint changelogs from completed Linear tickets with Claude Cowork

Team operationsClaude Cowork

The problem

Writing release notes every sprint means rereading every finished ticket and translating it into user-facing language.

Tools needed

• Claude Cowork (recurring task)
• Linear (via MCP)
• Your changelog / publishing tool (via MCP)

Step-by-step recipe

1. Connect Claude to Linear and to your changelog destination through MCP.
2. Create a recurring Cowork task for the end of each sprint (every two weeks in the source).
3. Have Claude read completed issues and decide which ones are user-facing.
4. Ask it to draft changelog copy from the ticket descriptions and comments.
5. Define rules for when an update also deserves an email or in-app announcement, and review before publishing.

Copyable prompt

Read all Linear issues completed in the sprint ending [DATE] for team [TEAM].
1. Keep only user-facing changes; list internal ones separately so I can check.
2. Group them as New, Improved, Fixed. One line each, written for customers, no ticket jargon.
3. Recommend whether this release deserves an email or in-app announcement, using this rule: [RULE].
Save as a draft. Do not publish until I approve.

What the builder reported

The PM says it replaced about an hour of manual work per sprint and that the writing is better because Claude includes details they used to skip. They still review it before shipping.

These are the source author's own claims. AgentRecipes has not tested or verified them.

Watch out for

• You need two MCP connections (Linear and the publishing destination) plus explicit rules for bigger announcements.

Source

More team operations recipes