Use casesStatus updates

The daily standup summary, written before the day starts

Mitra can write your daily standup summary automatically: describe the post you want, and an agent reads Linear and GitHub each weekday morning and publishes it to Slack. The agent groups the update by person and puts anything blocked at the top. Every run is recorded step by step, so you can see exactly what went into the post.

Runs: Weekdays at 8:45am
Used by: Ops / Chief of Staff · Engineering · Product Managers

The prompt

Every weekday at 8:45am, check what moved in Linear and what merged in GitHub since yesterday morning, then post a short standup summary to #standup in Slack, grouped by person, with anything blocked called out at the top.

Linear

GitHub

Slack

Build this agent

200 credits to start · no credit card

What the agent actually does.

Read what moved in Linear
The agent collects every issue that changed status, changed hands, or picked up a comment since yesterday morning.
Read what shipped in GitHub
Pull requests merged, opened, or still waiting on a review in the same window get pulled in alongside the issues.
Group the update by person
Each person gets one short block: what moved, what shipped, and what they picked up next. No per-repo dumps, no raw issue lists.
Lift the blockers to the top
Blocked issues and stalled reviews go above the per-person blocks, where they get read, rather than buried at the bottom of the post.
Post it to #standup
The summary lands in Slack before the meeting, so the meeting can be about the blockers instead of the recap.

Make it yours.

For the ops lead or chief of staff who opens Linear and GitHub every morning to hand-write a post the team skims once. Change any of this by saying so — there is nothing to rewire.

Send the summary as a direct message to each team lead instead of posting it in one channel.
Add a Friday run that covers the whole week and posts to the company channel.
Stay quiet on mornings when nothing moved, rather than posting an empty update.

Questions, answered.

Can a standup bot replace our standup meeting?

Mitra replaces the recap, not the conversation. The agent posts what moved in Linear and GitHub before the meeting, so the time goes to blockers and decisions rather than going around the room. Some teams keep a short call; others drop to two a week.

How does an automated standup know who is blocked?

Blocked work has to be visible in Linear or GitHub for the agent to find it: a blocked label, a stalled status, a pull request with no review. Mitra reads those signals and lifts them to the top of the post. Work blocked only in someone's head stays invisible.