All use cases

Work

Manager, developer, reviewer: three bots with handoff rules

Ten fancy job titles still leave you chasing unfinished handoffs.

Share

What hurt

Mac (@MacBuildsDaily) describes a delivery setup: Manager clarifies and assigns, Developer implements and records checks, Reviewer tests against acceptance criteria. A handoff is complete only when the receiver has the brief, can access context, and acknowledges the next action. Put each task where the work lives. Not affiliated with xAI.

What to install or create

Three bots + shared task tracker. Define boundaries and handoff done-when. You approve merges/releases.

Bots

  • Manager

    Clarifies, prioritizes, assigns. Does not implement.

  • Developer

    Implements agreed change; records checks.

  • Reviewer

    Tests vs acceptance; reports gaps. Never ships alone.

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 https://x.com/MacBuildsDaily/status/2109475381283868769 (credit @MacBuildsDaily).
  2. 2Create three bots with the boundaries above.
  3. 3Write handoff done-when: brief + access + acknowledged next action.
  4. 4Put every actionable task in the tracker the work already uses.
  5. 5Run one small change through Manager → Developer → Reviewer before wider use.

Approval fence

Do not merge, ship, or message customers without your yes.

What to tweak

Steal the three-role loop and the handoff definition. Titles without receivers are theater.

Source

Mac @MacBuildsDaily · 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