Work
A 20-bot startup org as a mini course: front doors, one job each, standing orders
Twenty bots without structure means overlap, noise and numbers nobody trusts.
What hurt
Nabil Kazi (@nQaze) runs BugSmash operations on about 20 single-job bots plus a Chief of Staff that designs the org, and wrote the whole setup up as eight lessons. Not affiliated with xAI.
What to install or create
The Chief of Staff keeps the roster, rewrites instructions and decides ownership (numbers go to Analyst, competitors to Observer). One Morning Brief bot owns the 8am list. Routines run at waking hours, at a coarse cadence, and stay silent when there's nothing to report. Shared memory holds company facts (newest fact wins); critical rules also live in each bot's instructions.
Bots
Chief of Staff
Keeps the roster, writes every bot's instructions, cuts overlaps.
Morning Brief
The only bot that sends the weekday 8am list.
QA
Smoke-tests the product in a real browser, silent when green.
Plugins
Calendar
Optional
Gmail
Optional
Notion
Optional
Browser
Optional
Routines
Morning Brief. 8:00 weekdays. One list of what needs you.
QA smoke test. 10:00 weekdays. Test key flows; report only on failure.
The prompt
Standing orders for every bot (author-quoted)
Quoted from @nQaze — as published. Do not invent a second system prompt.
LESSON 7: Standing orders for every bot 1. Drafts only. I press send. 2. Never invent numbers 3. Say UNKNOWN instead of guessing 4. Stay quiet unless something needs me 5. No em dashes
How to build this from scratch (author-quoted)
Quoted from @nQaze — as published. Do not invent a second system prompt.
LESSON 8: How to build this from scratch 1. Start with one front door bot you talk to 2. Add one scheduled bot that's silent when things are fine. 3. Add specialists for jobs you repeat 4. Give each one scoped instructions: what it's for, what's out of scope, who it escalates to, and a never-invent rule 5. Let one bot own the morning list 6. Add an orchestrator once you have more than a handful, to keep roles from overlapping 7. If you correct a bot twice, turn it into a standing rule
First run
- 1Read https://x.com/nQaze/status/2108654960955338992 (credit @nQaze).
- 2Start with one front-door bot you talk to, and link your tools (communication tools read-only).
- 3Add one scheduled bot that is silent when things are fine, then specialists only for jobs you repeat.
- 4Paste his five standing orders into every bot's instructions.
- 5Once you have more than a handful, give one orchestrator the job of keeping roles from overlapping.
Approval fence
His standing order is drafts only: he reads and presses send himself. Communication tools are linked read-only.
What to tweak
If you correct a bot twice, turn it into a standing rule.
Source
Nabil Kazi @nQaze · Original post
Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.
Pro pack
Want the full setup, not just the idea?
Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.