Draft a changelog every sprint from finished tickets
Idea + starter prompt, not run by us yet
For: Product managers who write release notes by hand every two weeks
A product manager has a Cowork job on a two week timer. Using MCP connections, it reads finished Linear issues, decides which ones users will notice, drafts changelog text from ticket descriptions and comments, and suggests whether the release also deserves an email and in-app notice. The PM says it replaced about an hour per sprint and the notes now carry details they used to leave out.
Steps
- Connect Cowork to your ticket tool and to where you publish notes.
- Write rules for which changes count as user facing.
- Write rules for when a release deserves an email or in-app notice.
- Have it draft the changelog and stop for review.
- Read and approve the draft before anything is published.
Starter prompt
Read the issues marked done in [ticket tool] for [sprint or dates]. Pick the ones users will notice and explain why. Draft a short changelog in plain language from the ticket descriptions and comments. Then say whether this release should also get an email or in-app notice, based on [rules]. Save it as a draft. Do not publish or send anything until I approve.
Original post: Reddit · found via agentusecases.ai. Written up in our own words. We haven't run it, so test it on made-up data first.