Give your Grok Bots office hours so questions wait for a briefing instead of interrupting you
by PaperChaseWebb
A builder shared a prompt for a Chief of Staff bot that sorts every bot notification into urgent, decision and FYI, batches decisions into two daily review windows, rolls FYI into one end-of-day summary, and flags approvals that would expire before the next window.
- Price
- Free
- Difficulty
- Beginner
- Setup
- 15 min
- Format
- .md file
give-your-grok-bots-office-hours-so-questions-wait-for-a-briefing-instead-of-interrupting-you.md · 3 KB · direct download, no signup
What you end up with
The step people skip is the expiry check: batching approvals is only safe if nothing time-sensitive quietly expires while it waits.
What you get
- A plain-language summary of the workflow
- A fill-in prompt template
- What to watch out for
- A link to the original source
Who it is for
Builders who already use AI agents and want a proven workflow they can copy into their own project.
Works with
Solid chips: the agent is named in this listing's own tools list. Dashed chip: Plain Markdown, so it also pastes into other agents such as Grok Bot, Hermes, OpenClaw or Muse. We list those as compatible by format only, not as tested.
Tools needed
Cost to run: Free with the agent plan you already use.
Time to result: One working session
How it works
Have one bot list every bot and routine that sends you questions, appr
Have one bot list every bot and routine that sends you questions, approvals or updates.
Expected: Done before you move to the next step.
Sort each into urgent, decision or FYI, and write what counts as urgen
Sort each into urgent, decision or FYI, and write what counts as urgent for each bot.
Expected: Done before you move to the next step.
Pick two daily review windows and merge decisions into one briefing wi
Pick two daily review windows and merge decisions into one briefing with context, a recommendation and the cost of waiting.
Expected: Done before you move to the next step.
Roll FYI updates into a single end-of-day summary
Roll FYI updates into a single end-of-day summary.
Expected: Done before you move to the next step.
Flag approvals that expire before the next window and schedule that wo
Flag approvals that expire before the next window and schedule that work for when you are available.
Expected: Done before you move to the next step.
Change no routine or notification setting until you approve the plan
Change no routine or notification setting until you approve the plan.
Expected: Done before you move to the next step.
Sample prompt from the pack
Apply this workflow to [your project]: 1. Have one bot list every bot and routine that sends you questions, approvals or updates. 2. Sort each into urgent, decision or FYI, and write what counts as urgent for each bot. 3. Pick two daily review windows and merge decisions into one briefing with context, a recommendation and the cost of waiting. 4. Roll FYI updates into a single end-of-day summary. 5. Flag approvals that expire before the next window and schedule that work for when you are available. 6. Change no routine or notification setting until you approve the plan. Stop and ask me before anything irreversible: deploys, payments, sends or deletes.
Adapted by PaperChaseWebb. Not the original author's prompt.
Free preview of the file
# Give your Grok Bots office hours so questions wait for a briefing instead of interrupting you PaperChase agent use case (free feed entry), version 1.0. Source: [Michael Fenech (@Michael_Fenech_)](https://x.com/Michael_Fenech_/status/2115884875844624558), 2026-10-29. ## What they did He asks the Chief of Staff bot to list every bot and routine that pings him, sort each message type into urgent, decision or FYI, and propose two daily review windows. Decisions arrive as one briefing with context, a recommended action and the cost of waiting. FYI items go into an end-of-day summary. Each bot gets written escalation rules for what may interrupt outside office hours, and the bot checks which approvals would time out before the next window so that work is scheduled when he is around. Nothing changes until he approves the plan. ## Worth knowing The step people skip is the expiry check: batching approvals is only safe if nothing time-sensitive quietly expires while it waits. Keep security, money and outage alerts in the urgent lane no matter what the schedule says.
Worth knowing
- The step people skip is the expiry check: batching approvals is only safe if nothing time-sensitive quietly expires while it waits. Keep security, money and outage alerts in the urgent lane no matter what the schedule says.
- Figures are as reported by the original author and were not re-measured by us.
Questions
Where does this come from?
A public post credited to Michael Fenech (@Michael_Fenech_). Source: https://x.com/Michael_Fenech_/status/2115884875844624558
Is it free?
Yes. Feed entries are free to read and download.
Details
Version 1.0 · Updated Oct 30, 2026 · Markdown version of this page
License: Personal and commercial use. Credit the original source when you share the workflow. Download terms
Related
AGENTS.md, CLAUDE.md and Cursor rules starter files
Six fill-in instruction files for coding agents (base, Next.js plus Supabase, FastAPI, browser game, CLAUDE.md pointer, scoped Cursor rules), an Approvals section that makes the agent stop and wait for your yes, a table of what Grok Bot, Claude Code, Codex, Hermes and Cursor each read, a read-only checker for your rule files and 9 prompts to write, trim and test your own.
Ask-first rules for AI agents: hard nos, approval cards and a test set
Paste-in rules that make an agent ask before it sends, spends, posts or deletes, define what a real yes is, and stop retries after a no, plus 12 test scenarios to check it.