Turn finished Dart tasks into a weekly changelog doc

Every Friday at 4pm, I want an agent to write our team's weekly changelog and save it as a doc inside Dart. Run this on a cron schedule set to Friday at 4pm.

Start with Dart Get User Space Configuration to load our workspace setup. I need the list of dartboards and the exact status names this workspace uses, because status names vary between workspaces and ours may not literally be called Done. Work out from that configuration which statuses mean a task is finished, and use those resolved names for the rest of the run instead of assuming a default.

Then use Dart List Tasks to gather every task that moved into one of those finished statuses in the last seven days. Page through the results until you have them all. Group the tasks by dartboard, so that product, engineering, and operations each end up as their own section of the changelog.

The writing quality is the whole point of this workflow, so do not paste raw task titles into a list. Rewrite each item in plain, customer readable language that somebody outside the team would understand. Where several tasks describe one piece of work, collapse them into a single line rather than repeating near duplicates. Open the changelog with the two or three most significant things shipped this week, called out above the per team sections.

Also use Dart List Docs to find last week's changelog doc, and compare it against this week's finished work so you can note anything that was expected last week but slipped. If nothing slipped, leave that part out rather than padding the doc.

Skip chores and internal maintenance tasks such as dependency bumps, refactors, and routine cleanup. The one exception is a quiet week: if nothing customer facing shipped, include the maintenance work so the changelog is never empty, and say plainly that it was a maintenance week.

Save the finished changelog with Dart Create Doc, titled with the week ending date, for example "Changelog, week ending 7 Aug 2026". The doc is the primary artifact of this workflow.

Finally, post a condensed version to our team channel using Slack Bot Send a Message. Keep the Slack post short: the headline items plus a sentence of context, and a link back to the new Dart doc for the full changelog. Use the Slack Bot integration for this, not the user level Slack integration.