The manager bot only points

Most people still talk to one Grok Bot. That is a clerk sitting at one desk, taking every kind of question.

A setup that actually moves work looks more like a small shop. One manager. A few leads. Workers who each own one job. You say yes before anything leaves the building.

The manager does not write the code. It does not cut the video. It does not send the invoice. It holds the map of the other seats and points. That is the whole job.

The list of seats

Write it on paper before you open another chat.

• One manager. Knows every bot you run. Takes a messy ask. Names the seat. Stops when it does not know.
• A few leads. Each owns a lane: schoolwork, inbox, research, publishing. They break work into short briefs. They do not do the brief themselves.
• Workers. One job each. One feature. One queue. One output file. They may start a background helper for heavy work. They come back with proof.

If you cannot name the seat, you do not need another bot. You need a sentence.

What the manager may do

Read the board. Name the next job. Pick a lead or a worker. Write a short brief that stands on its own. Collect proof. Ask you when a step cannot be undone.

What the manager may not do: ship code, send mail, spend money, invent a new seat, or keep a ten-minute job in its own chat.

That last rule is the one people skip. A manager that does the work becomes the fat bot again. Old notes pile up. The budget moves. The map goes stale.

Trust is not a vibe

You do not trust a team because it talks like a colleague. You trust it because the work can be checked.

• Proof. Every finished job leaves something you can look at: a file, a screenshot, a link, a change list. No proof, not done.
• Saved steps. Teach a worker how a careful person on that job actually works. Point at those steps. Do not re-explain them in chat.
• Files a bot can read. A board with named boxes beats a novel in the profile. One folder per job beats a shared dump nobody owns.

If the project, the inbox, or the board is a maze, the worker will wander and you will pay for the walk. Make the path obvious. Then the seat can stay small.

Hand off, then you say yes

The manager writes a brief. A lead picks a worker. The worker starts a background helper when the job needs a computer of its own. Those can run at the same time.

You do not sit in the worker chat and coach every keystroke. You wait for the packet: what changed, how to check it, what is still blocked.

Then you stamp. Approve. Reject. Send back with one note. That is the human job now. Managing digital helpers is not a slogan. It is a review queue.

Related: /blog/token-waste-is-context-bloat and /blog/hire-specialists-until-the-buildout

Copy-paste manager rules

Paste this into a fresh Grok Bot after you name it. Fill the list. Do not paste secrets.

Job: manager for <PROJECT>. You route. You do not do the work.

Team:
- Leads: <LANE: BOT NAME>
- Workers: <JOB: BOT NAME>

When I give you an ask, do this:
1. Name the outcome in one sentence.
2. Pick the smallest seat that can do it. Do not invent a new seat.
3. Write a short brief: goal, sources, output file, stop rule.
4. Hand it off. Keep this chat short.
5. Collect proof. If there is no proof, the job is not done.
6. Stop and ask me before anything leaves the building: send, spend, merge, publish, delete.

Never carry a worker's notes in this thread. Never do a ten-minute job yourself. Never start extra routines. Stay quiet when there is nothing to route.

A first week that will not drown you

• List the jobs you already dump on one bot. Pick three. That is the starting team.
• Name a manager. Paste the rules. Give it the map. Approve nothing except the plan.
• Stand up one lead and two workers. Write each job in the profile. One sentence.
• Run one real loop: ask the manager, get a brief, get proof, say yes yourself.
• Kill any worker that cannot show proof. Kill any manager that starts doing the work.
• Only then add a seat. Never add a seat because the last chat felt busy.

Why this belongs here

A setup is a team list you can read. The manager routes. Leads break work. Workers finish one job. You say yes.

Main bot: /prompts/grok-bot-gm-desk
How a setup runs: /desks
Smaller jobs, quieter loops: /blog/token-waste-is-context-bloat