Get one daily status briefing from a team of Grok Bots
Overview
Michael Fenech's prompt makes one Grok Bot your chief of staff and has it build a daily update from a shared log the other bots write to. The briefing sorts work into what needs your decision, what is blocked, what is finished, what is under way and what has gone quiet. It checks finished work against the real source, such as a sent folder, marks anything it cannot confirm, and shows you a sample before you schedule it. You add the logging rule to each bot yourself; the prompt walks you through it.
Use cases
Prompt
Copied 0
Help me set up a daily briefing across my Grok Bot team. You own this process as my Chief of Staff. First, help me choose a shared update log each Bot can access. Prepare this instruction for me to add to each Bot: ‘Whenever a job changes state, add an entry to the shared log with the job, owner, state, evidence link, next step and timestamp. Use these states: needs decision, blocked, done or in progress.’ Don’t assume you can change another Bot’s instructions. Walk me through applying the rule to each one. Build the briefing from that log, using these sections: 1 - Needs my decision. Explain the decision, your recommendation and what’s waiting on my answer. Include any verified deadline. 2 - Blocked. Show what’s stuck, why, who can unblock it and the next action. Distinguish waiting on me from waiting on another Bot, missing information or an outside response. 3 - Completed. Verify completion against the live source wherever possible. For an email, check the sent folder rather than trusting a Bot’s note. Link to the result or evidence. ‘Email prepared’ is different from ‘email sent.’ If you can’t verify completion, label it unverified. 4 - In progress. Show the owner, next milestone and what changed since the previous briefing. 5 - Status unknown. Move any unfinished job with no update for two days into this section. Include jobs whose status you can’t verify. Show the last confirmed update and how to check what’s happening. Silence doesn’t mean completion. Save every briefing in our agreed location so the next one can compare against it. On the first run, establish a baseline. Keep the update short enough to scan in a minute. Skip empty sections. Include each job once, even if several Bots contributed. Link to details instead of copying conversations. Finish with up to three actions that need my attention. Show me a sample first. Once we agree on the format, help me schedule it for my preferred time, timezone and delivery channel.
Can AI?
- Get one daily status briefing from a team of Grok BotsPaste into a general LLM and get one daily status briefing from a team of Grok Bots.