Todos los casos de uso

Trabajo

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.

Compartir

Qué dolía

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.

Qué instalar o crear

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

  • Calendario

    Opcional

  • Gmail

    Opcional

  • Notion

    Opcional

  • Navegador

    Opcional

Rutinas

  • Morning Brief. 8:00 weekdays. One list of what needs you.

  • QA smoke test. 10:00 weekdays. Test key flows; report only on failure.

El 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

Primer uso

  1. 1Read https://x.com/nQaze/status/2108654960955338992 (credit @nQaze).
  2. 2Start with one front-door bot you talk to, and link your tools (communication tools read-only).
  3. 3Add one scheduled bot that is silent when things are fine, then specialists only for jobs you repeat.
  4. 4Paste his five standing orders into every bot's instructions.
  5. 5Once you have more than a handful, give one orchestrator the job of keeping roles from overlapping.

Valla de aprobación

His standing order is drafts only: he reads and presses send himself. Communication tools are linked read-only.

Qué ajustar

If you correct a bot twice, turn it into a standing rule.

Fuente

Nabil Kazi @nQaze · Publicación original

Sin afiliación con xAI. No escribimos este prompt. Siguen aplicando las condiciones de las plantillas de terceros.

Explorar plantillas

Explorar planos de equipo

Paquete Pro

¿Quieres la configuración completa, no solo la idea?

Los paquetes Pro te dan el texto de la tarea, los prompts, los horarios y los tropiezos de los casos de uso más populares.

Ver Pro