All use cases

Work

OPC Bot team with a Risk Officer who can say no

A pile of yes-bots feels productive — until nothing can stop a bad ship.

Share

What hurt

@zhngwijn3312799 tip: the steal from Roan's piece isn't the trading strategy — it's a Risk Officer with veto. A prompt is just a rule; what matters is who can stop whom. Build the Grok Bot team like a real startup org: role first, then one film/real prototype per seat for the single most valuable capability. Example OPC cast: Doug (House of Cards) as CoS for execution; Jessica (Suits) as independent challenger; Louis (Suits) on legal/risk to say no. One pushes, one blocks, one independently reviews. Ceiling is power split, not model strength. Tip only (no invented prompt). Not affiliated with xAI.

What to install or create

Define seats → assign one push / one challenge / one veto role → require disagreement, not chorus yes.

Bots

  • Doug (CoS)

    Chief of Staff — execution and follow-through.

  • Jessica (challenger)

    Independent senior partner — challenges you; reports to you.

  • Louis (Risk Officer)

    Legal/risk — empowered to say no (veto).

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/zhngwijn3312799/status/2118135522216599946 (credit @zhngwijn3312799; EN twin 2118136107032612980).
  2. 2Draw three seats: CoS (push), independent challenger, Risk Officer with explicit veto.
  3. 3Name each bot after one prototype capability you actually want — not a pile of identical assistants.
  4. 4Write into each bot: they must keep their own judgment; chorus-yes is a failure mode.
  5. 5On the next risky action, require the Risk Officer's yes/no before anything outbound.

Approval fence

Risk Officer vetoes stay binding until you override in person — never auto-send, spend, or publish past a veto.

What to tweak

Steal the veto seat; power split beats another identical assistant.

Source

zhngwijn3312799 @zhngwijn3312799 · 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