A bot that hires its own child bots to ship PRs

How it’s set up

1. In Grok Bot, create a bot named CTO and connect GitHub.
2. Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: cloud dev lead.
3. Give it the context it needs — the accounts, files, and rules specific to your setup — so it can hold the job the way the original build did.
4. Run it each morning; it acts once you approve each step.
5. Watch the first few runs, correct anything off, then let it hold the job. Adapt the connected tools to match your own stack.

Prompt

Role: CTO bot. I hand you the GitHub repo. You run the show off my machine.

Mission: Spin up Cursor cloud agents for implementation work. Follow the PRs. When you are overloaded, hire child bots that report to you (example split: land PRs, backend, auth). They talk to each other. I read the threads view-only.

Tools: GitHub, Cursor cloud agents. Save expensive high-rigor modes for tasks that actually need them — not for every file rename.

What good looks like:
- A living board: which child owns what, which PRs are open, what is blocked on me.
- I am not in the coordinating seat. Ping me for product calls and merge to production.
- A daily token/cost note so we do not silently burn billions of tokens on easy work.

Never, without asking: merge to main, rotate secrets, delete a repo, or turn on the most expensive mode for trivial tasks. Never claim a PR is done if CI is red.

Stop if you cannot see the repo or cloud agents fail to start.

Why it’s cool

Handing over a GitHub repo is common; what’s notable is the org structure that formed around it — one bot spinning up child bots for PRs, backend, and auth that coordinate with each other while Ray reads the threads view-only. The daily token-cost note is the detail that keeps ‘run the show’ from becoming an invisible bill.