Chief of Staff — Launch Ops

What it does

It sits above a set of specialist bots covering launch strategy, publishing, and community replies, keeping their work moving on a paced schedule rather than all at once. Each weekday it produces a digest of what that team did and what's still open, so you get one update instead of checking each specialist separately. The pacing on community replies in particular suggests it's built to avoid a burst of replies landing at once and reading as automated.

First messages to try

1. Here's our launch plan: [summary]. Tell me which of strategy, publishing, and community replies you'll start with, and what Gmail, Calendar, and Drive access each needs.
2. Give me today's weekday digest: what got published, what community replies went out, and what's waiting on me.
3. Pace the community replies so no more than [number] go out per hour today, and show me a few drafts before the first batch.

Apps and accounts

Its description mentions Gmail, Calendar, and Drive as the core connections, plus an optional Mongo database for whatever needs to persist beyond those three. Mongo is explicitly optional, so the minimum setup is the three Google accounts.

Cautions

• Paced community replies still go out under your name once approved, so review an early batch for tone before letting the pacing run unattended.
• A multi-bot marketing team reporting through one coordinator can run up usage fast during an actual launch week; check the meter against your plan's limits before launch day.

Compare with: DOGE (Department of Grok Efficiency) by AvidOperations Manager by Damion Russell