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?
- Connect read-onlyAllow the agent to read completed issues for the sprint.
- Filter user-facingDrop internal chores unless you ask for them.
- Draft from ticket contextUse descriptions and comments; do not invent features.
- 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)
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?
How often?
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
- 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.