A manager Bot that never does the work itself

How this helps you

You manage one Bot instead of five, and every result gets checked before it reaches you.

✦ Try it

Rewrite your description: you are my [team] lead. You never do the work yourself. You break each request into small tasks, hand them to [Bot A], [Bot B] and [Bot C], check what comes back against the goal, and report to me. For big projects, write the plan in a [Notion] doc first and wait for my OK.

Fill in: [team] is the area (engineering, content). [Bot A] etc. are your worker Bots' names. [Notion] is wherever you keep plans.

What they did

Lauren Tan from the Grok Bot team tells Peter Yang she mostly talks to her chief of staff, which talks to an engineering lead Bot. She had her bot-designer Bot write the lead's description so its job is to break tasks into smaller pieces, delegate and supervise, and never do the work itself. The description even lists the other Bots it delegates to. Her engineer Bots in turn launch Cursor Cloud Agents, which lets her pick a faster model or more reasoning per task. For a big project she asks the chief of staff to plan the phases in a Notion doc first, and the work flows down from there. The official PM guide describes the same setup: an engineering manager Bot that does not code, five engineer Bots, and checks of output against the goal.

Who it's for: People with several worker Bots who want to give one instruction for a big project.

Before you start

Two or more worker Bots that already do good work on their own.
For coding work, Cursor Cloud Agents set up (see the related tip on watching them).

How to try it

Create or pick a lead Bot.
Rewrite its description around one job: break down, delegate, check (prompt below).
Name the worker Bots it may hand work to.
Start with a planning step in a shared doc before any work is handed out.
Ask for results to come back to you through the lead only.

What to expect

You send one request to the lead; it posts a plan, messages the workers, and comes back with checked results instead of doing a half-job itself.

Common mistakes

Leaving the lead free to do tasks. It will drift into doing them unless the description says never.
Auto-merging from day one. Lauren only lets PRs land unreviewed because the codebase was built for it.

Related tips

Start with a chief of staff Bot: Talk to one coordinator Bot and let it hand work to your specialist Bots.
One job per Bot: Give each Bot one job and a list of things it never does.
Watch coding work live and get recordings back: With Cursor connected, your Bot links you to the cloud agent live and sends screenshots and screen recordings.
Keep lasting rules in the description, not memory: Duplicate a Bot and the description comes along; memory starts empty.
Run a daily standup with your Bots in a group chat: Put your main Bots in one group chat and have your primary Bot ask each morning what everyone is doing today, so nothing slips.
Promote a Bot to director and let it build and run its own team: When one Bot has collected a lot of context, promote it: ask it to create three Bots that report to it, keep them away from you, and send you one Monday summary.