Weekly review of your Bot team: what shipped, what's stuck, what to change
Your Chief of Staff collects each Bot's daily five-line reports and, every Friday, tells you which Bots earned more scope, which need fixing, and what nobody owns.
What the Bot is set up to do
- Ask every specialist Bot to send the Chief of Staff five lines a day: what shipped, what is stuck, what needs a human.
- Add a Friday routine on the Chief of Staff for the review.
- Keep scope changes as proposals. You change permissions and Custom Rules yourself in Settings.
Prompt
Every Friday at 3pm, review the week for every Bot on this account.
Use their daily five-line reports, their routine runs, and the drafts I approved, edited or discarded.
For each Bot, tell me:
- Shipped: what it finished this week
- Stuck: what failed or waited on me, and why
- Clean runs: how many routine runs finished without my correction
- Recommendation: keep as is, give it more scope, narrow its job, or pause it, with one line of evidence
Then list any job two Bots both did, and any job no Bot owns.
Don't change any Bot, routine or permission. Propose, then wait for me.Business fit
Who this helps, and how:
- CreatorsNewsletter and creator teams with several Bots see which ones actually save time.
- AgenciesAgencies running a Bot per client get a weekly quality check before anything reaches the client.
- Solo foundersOwners promote a Bot from drafting to doing only after a clean record.
How to adapt it
Use the promotion rule from distort's onboarding guide: five clean runs in a row before a Bot gets more autonomy.
Read the review next to your weekly usage in Settings, and pause routines that cost more than they return.
Once a month, swap the review for an improvement sweep: send each Bot to find one improvement in its own area, and cap how many run at once.