Use case · Operations
Give the team one digest instead of ten status questions
To post a team digest to Slack with AI agents, set a routine on a Brainwrite bot that reads your tracker, repositories, and calendar. At the time you choose, it writes a short digest of what shipped, what is blocked, and what is coming up, and drafts the Slack message for your team channel. Posting waits for your approval unless you allow it.


Every weekday at 9:30, read Linear issues that changed since yesterday, pull requests merged in GitHub, and today's team events in Google Calendar. Draft a digest for #product with three sections: shipped, blocked, and today. Keep it under 150 words and ask me before posting.
Your Chief of Staff put a team on it
Atlas· Digest gatherer
Nova· Chief of Staff
- Shipped: 4 issues closed, 3 pull requests merged since yesterday
- Blocked: billing page redesign waiting on copy; owner and issue linked
- Today: design review at 14:00, release freeze at 17:00
- Digest for #product drafted at 128 words, waiting for your approval
DoneSaved as a routine: Weekdays at 9:30. It starts paused until you turn it on.

Team digest posted to Slack: done. Nothing sent.
- 1Shipped: 4 issues closed, 3 pull requests merged since yesterday
- 2Blocked: billing page redesign waiting on copy; owner and issue linked
- 3Today: design review at 14:00, release freeze at 17:00
The job
Doing it yourself, and handing it off.
Doing it yourself
Half of every stand-up is people reading out what the tracker already says. Managers ask in Slack what is blocked, people reply in threads, and the answers scroll away. A written digest would fix it, but someone has to collect the updates, write them up, and post them every day or week, and that someone is usually the busiest person on the team.
What the team does
- Read what moved in your tracker and repositories since the last digest
- List blocked work with the issue links
- Add upcoming deadlines and meetings from the team calendar
- Draft the Slack post in your format for your approval
What waits for you
- Whether each digest is posted, edited, or skipped
- Which channel it goes to
- Whether to allow posting without approval once you trust the format
The team
Who's on it.
Your Chief of Staff picks the specialists the job needs. Each has its own role, instructions, model, and app access.
AtlasIllustrated exampleDigest gatherer
Reads issues that moved in Linear or Jira, merged pull requests in GitHub, and upcoming events in Google Calendar.
NovaIllustrated exampleChief of Staff
Writes the digest in your format and drafts the Slack message for the channel you name.
How it runs
A run, step by step.
- 01
Connect the sources
Connect Slack, your tracker, GitHub, and Google Calendar. Grant read tools to the gatherer.
- 02
Set the format
Tell the Chief the sections you want, such as shipped, blocked, and coming up, and how long the digest should be.
- 03
Schedule it
Create a weekday or weekly routine. Each run starts fresh and drafts the digest.
- 04
Approve the post
Posting to Slack is an approval card unless you allow it for this routine.
What you'll connect
Apps this job uses.

Slack
Bots search Slack, summarise channels and threads, and post or schedule updates once you approve.

Linear
File clean Linear issues from bug reports, catch duplicates, review the current cycle, and draft project updates.

GitHub
Triage GitHub issues, review pull requests, read failing workflow logs, and draft release notes. Merges wait for you.

Google Calendar
Bots read your Google Calendar, find free slots, and create or move events. Invites wait for your approval.

Jira
Search Jira with JQL, file and transition issues, fill sprints, and get a plain summary of what blocks a release.
FAQ
Questions about Team digest posted to Slack
Can the bot post to Slack without asking each time?
Yes, if you choose. By default, sending a Slack message is an approval card. Once you trust the digest, you can allow that action, and Brainwrite's Always allow is narrow rather than a blanket permission. Many teams keep approval on for the first few weeks.
Does it work with Microsoft Teams instead?
Yes. The Microsoft Teams connector can list channel messages and send a channel message or a reply in a thread, which waits for an approval card unless allowed. Discord, Webex, and Telegram connectors can send messages too, also behind approval cards.
Will the digest run if my Mac is asleep?
Not as a local routine: Brainwrite must be running when it is due. Brainwrite Cloud runs your bots and routines on your own always-on cloud computer, so the digest is drafted on time, and the approval waits for you when you open the app.
Built on
Features this job relies on.
Routines
Run a bot's task once, on an interval, or on chosen weekdays, with a receipt for every run.
Approvals
Risky actions become cards you approve or deny in the conversation. Ask or Full Access per thread.
Connected apps
Gmail, GitHub, Slack, Notion and hundreds more via OAuth, with per-bot tool grants.
Chief of Staff
One bot takes your request, hands focused tasks to specialists, and returns a single summary.
Give your first job to Brainwrite.
Download the app, connect the AI you already pay for, and tell your Chief of Staff what needs doing.
macOS today. Windows and Linux are coming soon.







