Auto-Generate Daily Standup Prep with Grok Bot

Input: calendar, Notion agenda, Slack messages, Linear progress; Processing: Grok Bot aggregates per prompt; Output: one-page standup prep

Who

Team leads or engineers who manually gather info for daily standups

You get

Every weekday, 30 min before standup, receive one page: meeting time/link, agenda, release scope, each teammate's progress, items worth raising

You need

Grok Bot

Steps

1. Before the first real run

   Before the first real run, test with sample data and confirm with a human before any send/write/delete to external systems.

2. Configure and run the standup prep prompt

   Create or edit a Bot in Grok Bot and paste the following prompt into the instructions/system prompt field. Replace all angle-bracket variables with your actual values: - <your daily team sync time> → your standup time (e.g., 10:00 AM) - <Notion agenda database> → your Notion agenda database name or link - <team> → your team name or identifier Set trigger: every weekday, 30 minutes before standup. Save, and the Bot will auto-run at the scheduled time to aggregate info and output one page of standup prep.

   Execution prompt · Source text。Grok Bot system prompt / instructions field; replace variables before saving

   Copy prompt

   # Prep me for my daily.
   
   Run this every weekday, 30 minutes before <your daily team sync time>.
   Stay silent if the daily team sync is cancelled or declined. Send one
   line if it's async today.
   
   ## 01 / Gather
   01 Check the calendar for today's daily team sync. Grab the meeting
      link and any daily team sync plan.
   02 Find today's agenda page in <Notion agenda database> and read its
      host and agenda items.
   03 Pull release scope and dates from the latest planning notes. Check
      Slack for any scope or date changes leads posted since the last run.
   04 For each person on <team>, pull their Linear progress since
      yesterday: issues moved, blocked, or newly assigned.
   05 Pull important Linear comments on those issues since yesterday.
   06 Pull important Slack messages and threads aimed at <team>, or
      discussing the team's work, since yesterday.
   07 Find cross-team Slack threads about features <team> is working on.
      For each, give the latest update in one line.
   08 Pull the engineering digest and new work emails since yesterday.
   
   ## 02 / Format the result as
   - time and meeting link
   - agenda page and host
   - agenda items
   - at most 5 lines of release scope
   - each teammate's progress (one line each)
   - important Linear comments (at most 5)
   - important team threads (at most 5)
   - cross-team feature threads (one line each, with the latest update)
   - up to 3 prep bullets
   
   ## 03 / Rules
   Never invent status. If a source is empty or unavailable, say so in one
   line and move on.

# Prep me for my daily.

Run this every weekday, 30 minutes before <your daily team sync time>.
Stay silent if the daily team sync is cancelled or declined. Send one
line if it's async today.

## 01 / Gather
01 Check the calendar for today's daily team sync. Grab the meeting
   link and any daily team sync plan.
02 Find today's agenda page in <Notion agenda database> and read its
   host and agenda items.
03 Pull release scope and dates from the latest planning notes. Check
   Slack for any scope or date changes leads posted since the last run.
04 For each person on <team>, pull their Linear progress since
   yesterday: issues moved, blocked, or newly assigned.
05 Pull important Linear comments on those issues since yesterday.
06 Pull important Slack messages and threads aimed at <team>, or
   discussing the team's work, since yesterday.
07 Find cross-team Slack threads about features <team> is working on.
   For each, give the latest update in one line.
08 Pull the engineering digest and new work emails since yesterday.

## 02 / Format the result as
- time and meeting link
- agenda page and host
- agenda items
- at most 5 lines of release scope
- each teammate's progress (one line each)
- important Linear comments (at most 5)
- important team threads (at most 5)
- cross-team feature threads (one line each, with the latest update)
- up to 3 prep bullets

## 03 / Rules
Never invent status. If a source is empty or unavailable, say so in one
line and move on.