Use casesStatus updates

The daily standup summary, written before the day starts

Mitra writes your daily standup summary before the day starts. Each weekday morning the agent reads Linear and GitHub, groups what moved by person, and posts it to Slack with blocked work at the top. You can read back every run, step by step.

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

The prompt

Every weekday at 8:45am, read Linear and GitHub and post a standup summary to #standup in Slack, blockers first.

Linear

GitHub

Slack

Build this agent

200 credits to start · no credit card

What the agent actually does.

Read Linear
The agent takes every issue that changed since yesterday morning.
Read GitHub
It adds the pull requests merged, opened, or still waiting for a review.
Group it by person
Each person gets one short block instead of a raw issue list.
Put blockers first
Blocked issues and stalled reviews go above the per-person blocks, where they get read.
Post it to #standup
The summary lands in Slack before the meeting starts.

Make it yours.

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

Send each team lead their own summary instead of one channel post.
Add a Friday run that covers the whole week.
Say nothing on mornings when nothing moved.

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. Some teams keep a short call, and others drop to two a week.

How does an automated standup know who is blocked?

Mitra reads the blocked signals in your tools: a blocked label, a stalled status, a pull request with no review. The agent lifts those to the top of the post. Work that is blocked only in someone's head stays invisible.