When should you use it?
- One agent handles many unrelated jobs and its results have slipped
- You keep stepping in to correct or restart the same agent
- You are tempted to add another agent and want evidence first
Not for: A single agent with one clear job; Setups where agents keep no task history or routine records to review; Problems you already know are caused by a broken tool or missing login
What do you need, and what do you get?
You need
- A lead agent that can read your other agents' instructions, routines and recent history
- About two weeks of task history, including your corrections
- Any recorded usage or timing data
You get
- A workload map per agent with jobs, schedules, open work and dependencies
- Concrete examples of missed deadlines, repeat corrections and interruptions, with their impact
- A cause for each problem and a keep, simplify or split verdict per agent
- For any split, clear ownership, handoff rules and the extra cost it adds
- One trial plan with a baseline, success criteria and a way back
How does it work, step by step?
- Hand over the promptGive Fenech's prompt to your lead agent; it reports and changes nothing.
- Check the evidenceMake sure each problem it lists comes with a real example, not a guess.
- Try the cheap fix firstWhere the cause is unclear instructions or a bad schedule, fix that before splitting anything.
- Run one trialApprove the top candidate only, on representative tasks, against the current baseline.
- Compare and decideKeep the split if corrections and your interventions drop without a jump in usage; otherwise restore the original.
The prompt
The original prompt by Michael Fenech (@Michael_Fenech_), word for word, with a link to where it was published. Below it is our adapted version with fill-in blanks, if you want it. Works in Grok Bot, Claude Cowork, ChatGPT agent and others. Values in lime are placeholders.
Original prompt by Michael Fenech (@Michael_Fenech_)
Run a workload audit across my Bots. Find where their responsibilities are causing delays, mistakes or extra work for me, and whether splitting a Bot would help. 1: Map the actual workload. Review the last 14 days of accessible instructions, routines, task history and corrections. For each Bot, list its responsibilities, recurring jobs, run frequency, unfinished work and dependencies. Include time and usage where recorded. Flag missing evidence rather than guessing. 2: Find where the work breaks down. Look for missed deadlines, repeated corrections, jobs repeatedly interrupted by other requests, instructions from one job affecting another, and tasks that keep needing me to step in. Show specific examples and their impact. A long task list alone is not evidence that a Bot needs splitting. 3: Diagnose the cause. For each problem, distinguish between too many competing responsibilities, unclear instructions, missing access, unreliable tools and waiting for my approval. Explain why separating the work would help. If a clearer rule, better schedule or simpler workflow would solve it, recommend that first. 4: Give each Bot a verdict. Mark KEEP, SIMPLIFY or SPLIT, with the evidence and expected benefit. For SPLIT, identify the exact responsibility to move. Check whether an existing Bot could own it before proposing a new one. Keep closely connected work together when separating it would create more coordination than it removes. If evidence is insufficient, say what we need to observe before deciding. 5: Design the proposed split. Define what each Bot owns, what it must leave to the other, the information and tools each needs, and what completed work looks like. Specify when a handoff happens, what information travels with it and who owns the final result. Assign each routine and open task to one owner so nothing runs twice or gets lost. Include the extra messages, usage and supervision the split could introduce. Don’t assume two Bots will be faster or cheaper. 6: Propose a small trial. Choose the strongest candidate and define a trial using representative tasks, with a baseline from the current setup. Compare completion time, output quality, corrections, my interventions and usage where available. Set clear success criteria and a way to restore the original setup. Show me the ranked findings and trial plan first. Don’t create Bots, move tasks or change routines until I approve.
Exactly as published by Michael Fenech (@Michael_Fenech_) in X post: a workload audit that decides when one Grok Bot should become two.
Our adapted version (optional)
Fill in the blanks (optional; the copied prompt uses your values)
Review how work is divided among my agents on {platform} and tell me whether any agent should hand part of its job to another. Use the last {days} days of instructions, routines, task history and my corrections. For each agent, list its jobs, how often they run, open work and what it depends on; say where records are missing instead of guessing. Give real examples of late work, repeated fixes, interrupted jobs or tasks I had to rescue, and for each name the cause: overload, unclear instructions, missing access, unreliable tools or waiting on me. Recommend the smallest fix that would work, and only suggest a new or split agent when a clearer rule or schedule would not. For any split, give each agent one owner per routine and task, describe the handoff, and estimate the extra messages and usage. Propose one trial with a baseline, success measures and a rollback. Do not create agents or change anything until I approve.
What can go wrong?
- A long task list is not proof of overload. Ask for the specific failures behind each verdict.
- Two agents add handoffs and messages. Count that cost before approving a split.
- Moving a routine without naming one owner can make it run twice or not at all.
- Fourteen days may miss monthly jobs. Note anything that runs less often.
Our take
Adding another agent feels like the obvious fix when one starts dropping work, but it often trades one problem for a coordination problem. What we like about Fenech's audit is its skepticism: it asks for examples of real failures, separates overload from causes such as vague instructions or missing access, and recommends the cheaper repair first. The ownership rule matters too, since assigning every routine and open task to exactly one agent is what stops duplicate runs after a split. The trial design is the strongest part, because it compares against a baseline and keeps a way back, which turns a hunch into a measured decision. Our caution is data: if your agents keep little history, the audit will mostly report missing evidence, so let it run a week or two first. In our dry run with a fictional consultancy whose single operations agent handled invoicing, scheduling and a weekly newsletter, the audit traced three late invoices to newsletter drafting crowding the same mornings, recommended splitting off the newsletter, kept scheduling with invoicing, and proposed a ten-day trial with a rollback step, all without changing anything.
Where the time goes back: You fix the real cause of slipping work, avoid adding agents you then have to coordinate, and test any split on a small scale before living with it.
FAQ
Will it create new agents on its own?
What if the problem is unclear instructions?
Can I use this outside Grok Bot?
Source and credit
The original prompt on this page is by Michael Fenech (@Michael_Fenech_), shown word for word with a link to where it was published. The summary, notes and adapted version are ours.
- Original
- X post: a workload audit that decides when one Grok Bot should become two
- Creator
- Michael Fenech (@Michael_Fenech_)
- Published on
- X
- Original date
- Nov 1, 2026
- License
- Not openly licensed; the original prompt is shown word for word with credit and a link to the original
- Originally for
- Grok Bot
- AI dry run
- Nov 1, 2026: passed. Dry-run tested by our AI test agent on sample input. Evidence-based verdicts, cheaper fix considered, single owners, cost of the split counted, trial with rollback, no changes before approval.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Nov 1, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.