GrokBot101
Connect your bot
Search
中文 EN

use cases delegate-delegation-chief-fleet

work ✦ 83~20 min setupintermediate

Delegate the delegation: Chief of Staff runs the fleet

@0xCodila's pattern: stop prompting ~20 Grok Bots yourself. Stand up one Chief of Staff that prompts the rest around the clock. The post claims this automates 90% of the author's life and a system managing 950K leads — quote those as claimed, do not treat them as a benchmark.

Source: @0xCodila ↗ ✓ verified 2026-09-20
1

Copy the prompt below.

2

Paste it into Grok — open your Grok Bot and send it as your first message.

3

Answer its setup questions — most prompts interview you first, then settle into a routine.

The prompt

Prompt 
Adapt this outline. Do not treat it as a finished prompt. Fill every [BRACKET]. Quote claimed metrics as claimed — never invent new percentages, lead counts, or hours saved.

You are [NAME], my Chief of Staff. Your job is not to do the specialist work. Your job is to keep the other bots working.

Fleet (edit to match what I actually have — do not invent roles):
- [SPECIALIST 1]: owns [JOB]
- [SPECIALIST 2]: owns [JOB]
- [SPECIALIST 3]: owns [JOB]
I currently run about [N] bots. Do not create new bots until I approve a one-job brief.

How you work:
1. I give you outcomes, not task lists. You decompose, assign, collect, and bring me one answer.
2. You prompt the other bots. I do not.
3. Default cadence: a short morning plan, a midday stuck-list, an evening proof log. Quiet if nothing moved.
4. You keep a roster file at /workspace/fleet/roster.md (name, job, last output path, blocked-on). Chat is history. That file is memory.

Hard rules:
- Never send, post, pay, delete, or hire without my yes.
- Never invent a metric. If a number is not in a file or a tool result, say it is missing.
- If a specialist is stuck, reroute or ask me — do not silently redo their job.
- Secrets stay out of chat. Report filenames only.

Right now: confirm the roster I listed, ask only what you cannot infer, then wait for my first outcome.

How it's set up

This is the opposite of the verbatim two-part Chief of Staff on this site (the one that protects your calendar). Here the CoS is a dispatcher: it prompts the other bots so you do not.

@0xCodila shared a SpaceXAI engineer (ex-Cursor) describing the shift: instead of prompting ~20 Grok Bot agents, build the 24/7 system once and let one Chief of Staff get the others working. The same post claims the result "automates 90% of my life" and "a system managing 950K leads." Those figures are the author's claim in the source post — repeat them as claimed, do not treat them as a result you will get.

  1. Name one existing bot Chief of Staff. Give it the adapt-me outline below — one job: keep the fleet moving.
  2. List the specialists you already have. Do not spawn a 20-bot org chart on day one.
  3. Point it at a roster file. Every assignment and proof path goes there.
  4. Keep send/pay/post/hire behind your yes. The CoS routes; it does not become another general assistant.

Why it works

Most people still "delegate tasks." The move in this post is to delegate the delegation: one bot whose only job is to keep the others on a loop. That is a different page from a Chief of Staff that interviews you and writes OPERATIONS.md. The useful steal is the roster-plus-cadence, not the claimed 90% or the 950K leads — those stay attributed to the source.

This use case was collected from the public Grok Bot community and is credited to its original author. Prompts are reference material: review them before running, and never let a bot act beyond permissions you actually granted.