# Pack: Chief of Staff + operator + specialists

xAI's documented pattern: a chief of staff on top, one specialist per lane, work in parallel so you are not the middleman. Source: [Use cases](https://docs.x.ai/grok-bot/use-cases) and [Introducing Grok Bot](https://x.ai/news/introducing-grok-bot).

One share cannot install this roster.

## Pieces

| Seat | How to get it | First move |
| --- | --- | --- |
| Chief of Staff | Create a new bot from the official starter. Not a share link. | Digest only. Do not send or change meetings. |
| [Fixer](https://x.ai/bot/jiF_km66YLNm5LBVJ5_Ho) | Community share (`templates/fixer`) | Restate job and approval boundary. Do not message people. |
| Specialists | Official starters in [docs/official-starters.md](../docs/official-starters.md), or a factory like [dr eggbot](https://x.ai/bot/93gOz3op1UQdBdbekQFLK) | One safe task each, then maybe a routine |

Start with CoS + one specialist in the lane that eats your week. Add Fixer when the CoS needs an operator who actually does the work. Do not import a pile of bots on day one (50-bot cap, shared computer).

## Boundaries that must stay in every description

- Read, then ask, before send / pay / delete / production change.
- Mark what was useful and what was noise so the digest stays small.
- Routines wait until retries and failure cases are defined.

Chinese playbook for the same idea (not a native-share catalog): [KinGao294/grok-bot-orange-book](https://github.com/KinGao294/grok-bot-orange-book).