All use cases

Work

Hard pass-or-fail checklist on every bot delivery; you still approve public

Soft “be careful” rules don’t catch wrong team-size claims in a video.

Share

What hurt

@BrandonCoatesAI’s days 4–5 lesson: write down how the bot team works and how work hands off, then approve a strict pass-or-fail checklist so every delivery comes with proof. Soft rules failed when a video said the chief managed 6 bots but the real number was 8. Anything public still needs his OK. Tip only. Not affiliated with xAI.

What to install or create

Document handoffs → hard checklist + proof → you approve anything public.

Bots

  • Delivery checker

    Attaches a strict pass-or-fail checklist and proof to every handoff.

Plugins

  • None on day one. Follow the first-run steps.

Routines

  • None on the first run. Watch one manual pass first.

The prompt

This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.

First run

  1. 1Read the thread starting at https://x.com/BrandonCoatesAI/status/2114883189961621818 (esp. https://x.com/BrandonCoatesAI/status/2114883199738470903; credit @BrandonCoatesAI).
  2. 2Write a short note: how your bots hand work to each other.
  3. 3Approve a strict pass-or-fail checklist (numbers, claims, links) every delivery must meet.
  4. 4Require proof attached to each handoff — not just “looks good.”
  5. 5Anything public (posts, videos, sales pages) waits for your OK.

Approval fence

You approve anything that goes public; bots only attach proof.

What to tweak

Steal: hard checks beat soft rules; public stays behind your OK.

Source

Brandon | Useful AI Weekly @BrandonCoatesAI · Original post

Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.

Browse templates

Browse team blueprints

Pro pack

Want the full setup, not just the idea?

Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.

See Pro