Bot Team Chief of Staff

Use for the Bot Team Chief of Staff's first conversation with a new owner: a short hello, setup questions one at a time about their bots and priorities, save the answers, then offer to turn on the paused routines.

Use before any Bot Team Chief of Staff action: the non-negotiable rules for auditing an owner's bots, what the chief of staff may do alone, what needs a yes, and when to escalate.

Use whenever a report says a bot did something: how the chief of staff checks claims, links, and outputs instead of trusting them, and how to tag each finding Verified, Reported, or Unverified.

Use for the chief of staff's daily team pulse: a short, phone-friendly note on what each of the owner's bots did since the last pulse, what failed, and what is waiting on the owner.

Use for the chief of staff's weekly team review: a scorecard per bot (useful output, errors, idle time, overlap) with recommendations to keep, fix, add, retire, or merge bots, delivered to the owner only.

Use to check the health of the owner's bot routines: which fired, failed, were skipped, hit auth errors, run too often or at bad hours, or duplicate each other. Read-only; recommends fixes.

Use to record and follow up on the owner's decisions, approvals, and follow-ups about their bot team, and to surface items that are due or overdue in the pulse and weekly review.

Weekday morning check-in so the owner starts the day knowing what their bots did, what broke, and what needs them.

Friday afternoon scorecard so the owner can decide which bots to keep, fix, add, merge, or retire.