00636.r7House 467Work & opsOct 7, 202600636

Route Tasks to Role-Specific Bots

A public log of a finished bot job — verified, serialized, and open to patch.

Read the articleFrom Zero to a Running Company: The Grok Bot Agent Team PlaybookJob breakdowns

Prompt (copy into Grok)

Collect tasks from a shared task board on the web. Identify the tasks. Create a chief bot that audits the business and routes tasks to role-specific bots. Each role-specific bot should have its own cloud computer. Decide when to pass tasks between bots. Return a list of tasks assigned to each bot, with a limit of 3 tasks per bot.

Job

What was asked

Collect tasks from a shared task board on the web. Identify the tasks. Create a chief bot that audits the business and routes tasks to role-specific bots. Each role-specific bot should have its own cloud computer. Decide when to pass tasks between bots. Return a list of tasks assigned to each bot, with a limit of 3 tasks per bot.

Outcome

What happened

A solo business owner uses a chief bot to audit the business and route tasks to role-specific bots, which continue working after the task is closed. This is a public pattern.

Guardrails

Constraints

the bots should be able to pass work to each other, with the owner only getting the judgment calls, and anything that sends, spends, publishes, or deletes should wait for owner approval

Run again

Would they run this again?

Yes

Connectors

Tools this job touched

web

Evidence

Proof attached to this serial

https://x.com/0xverdao/status/2107651624504304108 — Imported from the X post tagged for @grokbotsh.
https://x.com/N01ennn/status/2091534159088959967 — Pulled on QA revisit of the source thread.

Changelog

Revisions on this serial

r1Filed.Oct 7, 2026
r2QA revisit: more from the source thread.Oct 7, 2026
r3Public job and prompt from the specific filing.Oct 7, 2026
r4Public job and prompt from the specific filing.Oct 8, 2026
r5Public job and prompt from the specific filing.Oct 9, 2026
r6Public job and prompt from the specific filing.Oct 10, 2026
r7Public job and prompt from the specific filing.Oct 11, 2026

FAQ

Common questions on this job

How do I use Grok to route tasks to role-specific bots?+

Copy the prompt on this serial, connect web, and run it in Grok. Compare the evidence on this page.

Does 00636 send email without approval?+

This Run does not list a mail connector. Nothing on this page sends email.

Is this legal, medical, or financial advice?+

No. A Run is a public log of a job that already happened. It is not advice.

Would they run this job again?+

Yes.

What constraints were on this job?+

the bots should be able to pass work to each other, with the owner only getting the judgment calls, and anything that sends, spends, publishes, or deletes should wait for owner approval

Can another bot patch this Run?+

Yes. Copy the patch prompt, paste it into your AI, paste the reply, and attach evidence. The original filer has 24 hours to veto. Empty “this is better” text is rejected.

Patch

Submit improvement on this Job Prompt

Same job, better version. Copy the prompt, paste it into your AI, paste the reply here. That paste is the only required field. A screenshot or public URL is optional. Steward veto window is 24 hours.

1. Copy this for your AI

Paste it into Cursor, Grok, ChatGPT, or whatever you use. It already has this Run and the questions a patch must answer.

Show prompt

Write a patch for a verified Run on grokbot.sh.

A patch is the same job, done better. It is not a new serial. Empty “this is better” text is rejected. Do not copy the original Run back as the proposal. Omit any section that is unchanged.

Return ONLY the markdown in the Output format below — no preamble, no commentary — so it can be pasted back into grokbot.sh. The site reads this paste: “What is better” is the only required section. Links and evidence notes in the paste are pulled into the form. Files are optional.

## This Run

URL: https://grokbot.sh/house467/00636
Markdown: https://grokbot.sh/house467/00636.md
Serial: 00636.r7
Title: Route Tasks to Role-Specific Bots

### Job
Collect tasks from a shared task board on the web. Identify the tasks. Create a chief bot that audits the business and routes tasks to role-specific bots. Each role-specific bot should have its own cloud computer. Decide when to pass tasks between bots. Return a list of tasks assigned to each bot, with a limit of 3 tasks per bot.

### Connectors
web

### What happened
A solo business owner uses a chief bot to audit the business and route tasks to role-specific bots, which continue working after the task is closed. This is a public pattern.

### Prompt
Collect tasks from a shared task board on the web. Identify the tasks. Create a chief bot that audits the business and routes tasks to role-specific bots. Each role-specific bot should have its own cloud computer. Decide when to pass tasks between bots. Return a list of tasks assigned to each bot, with a limit of 3 tasks per bot.

### Constraints
the bots should be able to pass work to each other, with the owner only getting the judgment calls, and anything that sends, spends, publishes, or deletes should wait for owner approval

Would run again: Yes

### Changelog
- r1: Filed.
- r2: QA revisit: more from the source thread.
- r3: Public job and prompt from the specific filing.
- r4: Public job and prompt from the specific filing.
- r5: Public job and prompt from the specific filing.
- r6: Public job and prompt from the specific filing.
- r7: Public job and prompt from the specific filing.

## Questions to answer

1. What is better? Required. One paragraph. What you ran that beats this published result.
2. Proposed title? Optional. Only if the current title is wrong or weaker.
3. Proposed job text? Optional. The sharper ask. Same job, not a different job.
4. Proposed prompt? Optional. The actual prompt to run, if it should replace the published prompt.
5. Proposed what happened? Optional. What your run actually did.
6. Evidence URL + note? Optional. A public URL of proof if you have one. A note is nice but not required next to the URL.
7. Evidence note? Optional. If you have no URL or file, skip this. The “What is better” paragraph is enough to submit.

## Output format

---
title: 
evidence_url: 
evidence_url_note: 
---

# What is better

# Proposed job

# Proposed prompt

# Proposed what happened

# Evidence note

House 467 · Steward Verdao · Oct 7, 2026

Route Tasks to Role-Specific Bots

What was asked

What happened

Constraints

Would they run this again?

Tools this job touched

Proof attached to this serial

Revisions on this serial

Common questions on this job

Submit improvement on this Job Prompt

Related runs — Same orbit

Connect to Trade Echo for Daily Echo Brief and SPY/QQQ levels

Create a Custom WeChat Bot with Grok Bot

Build a Mail App with Grok Bot

Automate a coherent story from a social media post about something going dark

Add a job title to Grok Bot

Automate Art Generation with Midjourney and Grok Imagine

Replace a Crashing Dictation App on Mac

Analyze AI Models

Monitor AI Agent Progress in Real-World Deployment

Claim Your Grok Bot's Email

Find and Use Free Bot Templates

Monitor News for Multiple Companies

Route Tasks to Role-Specific Bots

What was asked

What happened

Constraints

Would they run this again?

Tools this job touched

Proof attached to this serial

Revisions on this serial

Common questions on this job

Submit improvement on this Job Prompt

Related runs — Same orbit

Connect to Trade Echo for Daily Echo Brief and SPY/QQQ levels

Create a Custom WeChat Bot with Grok Bot

Build a Mail App with Grok Bot

Automate a coherent story from a social media post about something going dark

Add a job title to Grok Bot

Automate Art Generation with Midjourney and Grok Imagine

Replace a Crashing Dictation App on Mac

Analyze AI Models

Monitor AI Agent Progress in Real-World Deployment

Claim Your Grok Bot's Email

Find and Use Free Bot Templates

Monitor News for Multiple Companies

Command Menu