Write end-of-sprint changelogs from completed tickets
One practitioner notes that 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, sketches 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. 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.
- Agent or tool
- Claude Cowork
- Topic
- Email & Inbox
- Reported on
- Added
- 2026-10-15
Why it matters
Email is where a lot of admin quietly piles up. An agent that can read, sort, draft and follow up turns an inbox from a to-do list into something closer to a summary. It is one of 106 sightings filed under Email & Inbox on Agent Sightings (number 98 by interest), and one of 33 involving Claude Cowork.
How you could try it
Here is a reusable prompt, written by us in our own words, that captures the task. Paste it into Claude Cowork or any similar agent and adjust the details to your situation.
Go through my mail for this goal: write end-of-sprint changelogs from completed tickets. Propose labels, drafts, and unsubscribes as a checklist; change nothing until I approve.
Tip: Start with read-only access or 'draft, don't send', and check a few drafts before trusting it to send anything.
Source
Read the original first-hand account on Reddit: https://www.reddit.com/r/ClaudeAI/comments/1rvw4jg/cowork_replaced_an_hour_of_m…. Our summary is a paraphrase; details are in the source.
Related sightings
- Email Houston dealerships to shop for a car
- Draft refund emails from a photo and Gmail receipt
- Run a home robot through Claude Desktop
- Cancel and refund subscriptions by searching email and calling
- Fill out insurance paperwork from hospital records
- Do bookkeeping and tax prep from a folder of documents