# Turn finished Dart tasks into a weekly changelog doc

> Every Friday, an agent reads the week's completed work in Dart, writes it up in plain language, and saves it as a doc your whole team can share.

- Workflow type: agent
- Services: Dart, Slack Bot
- Categories: Product, Operations
- Published: 2026-08-04

## What it does

- Runs every Friday afternoon and gathers every task your team finished in the past seven days.
- Rewrites task titles into plain language a customer would understand, and merges closely related work into a single line instead of repeating near duplicates.
- Groups the update by team so product, engineering, and operations each get their own section, with the two or three biggest wins called out at the top.
- Saves the finished changelog as a doc inside Dart, then posts a short version to Slack with a link back to it.

## What you'll need

- A Dart account with your team's work tracked across dartboards
- A Slack workspace and a channel where the weekly update should be announced
- Statuses in Dart that mark work as finished, whatever you happen to call them

## Prompt

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.

## How to customize

- Change the timing. Friday at 4pm is a sensible default, but Thursday evening or Monday morning works just as well.
- Choose which dartboards become sections. Product, engineering, and operations are the starting point, but you can add design, support, or any other team.
- Decide whether routine maintenance work shows up, and pick which Slack channel gets the condensed summary.

## FAQ

### Does this create a task in Dart, or an actual document?

An actual document. The changelog is saved as a doc inside Dart, titled with the week ending date, so it lives alongside your tasks and meeting notes rather than becoming another to-do. The Slack message is just the announcement that points back to it.

### Our finished column is not called Done. Will this still work?

Yes. The agent reads your workspace setup first to learn the status names you actually use, then works out which ones mean a task is complete. Nothing is hardcoded to the word Done, so custom names like Shipped, Live, or Released are picked up automatically.

### Will it just paste our task titles into a bullet list?

No, and that is the main point of it. Task titles are usually written for the person doing the work, not the person reading about it. The agent rewrites each item in plain language, collapses several related tasks into a single line, and leads with the two or three most significant things that shipped.

### What happens in a quiet week when we only shipped small fixes?

Routine maintenance and chores are normally left out to keep the changelog readable. But if nothing else shipped that week, they get included so the update is never empty, with a plain note that it was a maintenance week.

### Can we edit the changelog before sharing it more widely?

Yes. The doc is a normal Dart doc, so anyone on the team can open it and edit it. The Slack post is an internal heads-up with a link, which makes it easy to polish the doc before sending it to customers or dropping it into a release announcement.

Use this prompt in General Input: https://www.generalinput.com/prompts/turn-finished-dart-tasks-into-a-weekly-changelog-doc