Write end-of-sprint changelogs from completed tickets

A PM has Claude Cowork read completed Linear tickets, pick what matters, draft the update and suggest email or in-app format, replacing about an hour per sprint.

Done withClaude Cowork

What they did

The PM set up a recurring Claude Cowork task that runs every two weeks. Through MCP connections, Claude reads completed Linear issues, decides which ones are user-facing, drafts changelog copy from ticket descriptions and comments, publishes it, and then chooses whether the release also merits an email and in-app notification; the PM says they usually just review and send it.

How it went

It replaced about an hour of manual work each sprint, and the PM says the writing is better because Claude includes details they used to skip. They still review it before shipping, but say that happens 90% of the time rather than writing it themselves.

Worth knowing

The key catch is the MCP setup: Claude needed one connection to Linear and another to the publishing destination, plus rules for when bigger updates should trigger email and in-app announcements.

Source: Reddit · Apr 5, 2026