All use cases

Work

Status files, not group chat — one lead routes quiet specialists

Put bots in a group chat and every message wakes everyone — credit gone by noon.

Share

What hurt

@livesanches tip (X Article on an 11-bot solo startup): first mistake was a bot group chat — every message woke every bot. Fix: each bot writes a 5-line status file at end of every task (Done, proof, next, waiting on, updated at). Bots read files, not each other's chatter. One lead routes; others stay quiet until called. Corrections become one-line rules in a shared lessons file. Tip/checklist only. Not affiliated with xAI.

What to install or create

One job + status file per bot → lead routes by file → lessons file for corrections → you still press every external button.

Bots

  • No new bot. Follow the first-run steps.

Plugins

  • None on day one. Follow the first-run steps.

Routines

  • None on the first run. Watch one manual pass first.

The prompt

This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.

First run

  1. 1Read https://x.com/livesanches/status/2118470328246489391 (credit @livesanches).
  2. 2Pick one lead bot and two specialists; ban group-chat handoffs between them.
  3. 3Require a 5-line status file after every task: Done, proof, next, waiting on, updated at.
  4. 4Have the lead read those files to route work — specialists stay quiet until called.
  5. 5When you correct a bot, add one line to a shared lessons file that every bot reads before the next task.

Approval fence

Bots draft only — never publish, send, spend, or merge without your yes.

What to tweak

Steal the 5-line status file; quiet bots only wake when the lead hands them work.

Source

Felipe Sanches @livesanches · Original post

Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.

Browse templates

Browse team blueprints

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.

See Pro