← Back to library

Publish the sprint changelog from completed tickets

u/Senseifc on r/ClaudeAI, a PM, used Claude Cowork on a two-week schedule to pull finished Linear issues, draft changelog copy from ticket details, and publish—with email or in-app notes only when the update was large enough. They still make the go-live call.

  • OutcomeOn a schedule, pull completed tickets, decide which are user-facing, draft the changelog from ticket context, and wait for your review before publishing or emailing users.
  • SetupUnder an hour
  • LevelIntermediate
  • Creditu/Senseifc on r/ClaudeAI
View original
Works with
Claude CoworkClaudeChatGPT

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 24, 2026

When should you use it?

  • End-of-sprint notes always slip
  • Ticket text is richer than what you remember when rushing
  • You can connect the tracker read-only

Not for: Publishing without a human skim; Customer emails for every tiny fix

What do you need, and what do you get?

You need

  • Project tracker with completed issues
  • Voice and audience for the changelog
  • Publish destination

You get

  • Draft changelog grouped by theme
  • Recommendation: silent publish vs email
  • Nothing live until you approve

How does it work, step by step?

  1. Connect read-onlyAllow the agent to read completed issues for the sprint.
  2. Filter user-facingDrop internal chores unless you ask for them.
  3. Draft from ticket contextUse descriptions and comments; do not invent features.
  4. You publishReview, add the header image if needed, then release.

The prompt

Our own prompt, inspired by u/Senseifc on r/ClaudeAI and written to work in Claude Cowork, Claude and ChatGPT. Values in lime are placeholders.

Fill in the blanks (optional; the copied prompt uses your values)

Prompt4 variables
Sprint {sprint_id}. Completed issues: {issues}.
Write a changelog for {audience} in our voice ({voice}).
Only user-facing changes. Group by theme. Each item: one sentence benefit + ticket id.
End with publish_recommendation: silent | email | in-app, with reasons.
Do not publish or email. Flag tickets with too little detail as NEEDS_HUMAN.

Inspired by u/Senseifc on r/ClaudeAI: cowork replaced an hour of my most hated PM task every sprint and i didn't have to write a single script. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • Internal refactors labeled as user benefits confuse customers.
  • Schedule without approval becomes accidental announcement.

Our take

Scheduled Cowork jobs shine on recurring PM chores. The poster's review-then-ship habit is mandatory in our version. In our dry run on 18 sample tickets, it drafted a 6-item changelog, marked 2 as email-worthy, and left 7 internal items out. Keep publish behind your click even when the draft is excellent. Separate user-facing notes from internal chores every time. If ticket text is thin, send it back to engineering instead of inventing a benefit. Header images can stay manual. Match the cadence to how often you actually ship. Keep publish behind your click even when the draft is excellent. Separate user-facing notes from internal chores every time. If ticket text is thin, send it back to engineering instead of inventing a benefit. Header images can stay manual. Match the cadence to how often you actually ship. Keep publish behind your click even when the draft is excellent. Separate user-facing notes from internal chores every time. If ticket text is thin, send it back to engineering instead of inventing a benefit. Header images can stay manual. Match the cadence to how often you actually ship.

Where the time goes back: The hour of sifting tickets becomes a review of a draft that already used the ticket detail you usually skip.

FAQ

Must it be Linear?
Any tracker with completed issues and enough description works.
How often?
Match your sprint or weekly ship cadence.

Source and credit

Inspired by u/Senseifc on r/ClaudeAI. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
cowork replaced an hour of my most hated PM task every sprint and i didn't have to write a single script
Creator
u/Senseifc on r/ClaudeAI
Published on
Reddit
Original date
Mar 17, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
Claude Cowork
AI dry run
Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Review gate; no publish.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Are you the creator? Claim or correct this page.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminPrompt✓ AI dry run

Rewrite a task prompt to go deeper, not bigger

Before handing an AI an important piece of work, have it explain how a leading practitioner would approach the job, which raw inputs and methods they would use, and what independent check would prove the answer right, then rewrite your request around those answers before any work starts.

Credit: Felix Rieseberg

Minutes
Operations & AdminPrompt✓ AI dry run

Run a fast watcher and a slow watcher, and allow silence

Set an hourly narrow-signal watcher and a daily theme summary watcher, both allowed to report nothing instead of inventing updates.

Credit: Matt Palmer (@mattyp)

Under an hour
Operations & AdminSkill✓ AI dry run

Stress-test an idea with an honest devil's advocate

Get an AI to argue against your plan one serious objection at a time, offer real alternatives with tradeoffs, and openly mark each concern as resolved, narrowed or still open, so you end with a stronger plan or a better one.

Credit: u/wtfzambo on r/ChatGPTPromptGenius

Minutes
Operations & AdminPrompt✓ AI dry run

Turn your past AI corrections into rules for a skill file

Get a ranked list of the specific rules you keep teaching your AI, pulled from your own past chats, ready to drop into a reusable skill or instruction file.

Credit: Omer Feinholtz

Minutes
Operations & AdminPrompt✓ AI dry run

Chain skills with a yes-gate instead of one giant prompt

Assemble a daily pipeline: pick from a source, draft with a writing skill, wait for your yes, then hand to a planning or build skill.

Credit: Matt Palmer (@mattyp)

Under an hour