Turn completed tickets into sprint changelogs

A PM used Claude Cowork to read finished Linear tickets and draft customer-facing release notes every two weeks.

Done with Claude Cowork· Intermediate· Apr 2026

What they did
The PM set up a repeating Claude Cowork job on a two-week cycle. Using MCP links to Linear and the publishing tool, it checked completed issues, filtered for user-facing changes, and wrote changelog copy from ticket text and comments. It also suggested whether the release should go out as email, in-app messaging, or both.
How it went
The workflow saves about an hour each sprint. The PM says the drafts are stronger because Claude adds details they often left out, though they still review the copy before it goes live about 90% of the time.
Tips
This works best when the agent can reach both the ticket tracker and the place where updates are published. Set clear rules for when a release is big enough to trigger email or in-app notices, and make approval mandatory before any posting or sending.

Try it yourself with Claude Cowork

You are helping me prepare a sprint changelog. Review the completed tickets in [Linear project/team] from [date range]. Select the items customers would actually notice, ignore internal maintenance work, and draft a plain-language update for [email / in-app / both]. For each item, include a brief reason if you leave it out. Before you send, publish, or schedule anything, stop and show me the draft for approval.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.