All use cases

Engineering

One shared box: CoS dispatch, artifacts, human on the irreversible five

More bots is not what the official guide asked for.

Share

What hurt

madogiwacowork re-read the official Grok Bot guide. It does not say “add more bots.” Put one end-to-end owner on the job, add a specialist only when a stable specialist role appears (the stuck signal), hand off via artifacts on the shared computer, and let humans touch only what cannot be undone.

What to install or create

Minimum roster is one end-to-end owner. That seat is Chief of Staff: dispatch + the stop line — CoS does not do the work. Shared one computer. Hand off finished files under /workspace/<project-name>/, not chat paste. Human-only login handoff: password/passkey, 2FA, CAPTCHA, payment/KYC, or any site that demands a human — stop and return to you. Approval fence: send / purchase / delete / publish / production change. Done means the named artifact is in the named place. Paste his five-line CoS description (quoted on this page). A skill is run once by hand, saved as a skill, then hung as a routine. Author-quoted template from his Article — no invented extra prompt.

Bots

  • Chief of Staff

    Owns the job. Dispatch + stop line only — does not do the work. Adds a specialist only when a stable specialist role appears.

Plugins

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

Files

  • /workspace/<project-name>/ — finished artifacts live here. Hand off the files, not chat paste.

Routines

  • After a skill works once by hand: save it as a skill, then hang the routine.

The prompt

Author-quoted CoS description

Quoted from @madogiwacowork’s Article via https://x.com/madogiwacowork/status/2096721289599922688

・この仕事の持ち主は自分です。成果物は /workspace/(プロジェクト名)/ に置きます
・承認なしに、外部への送信・購入・削除・公開・本番の変更をしません
・パスワード、二要素認証、CAPTCHA、支払いが出たら止めて、人に戻します
・入力が無い、または古いときは進めずに、その旨を報告します
・完了の定義は「(成果物)が(置き場)にある状態」です

First run

  1. 1Read https://x.com/madogiwacowork/status/2096721289599922688 (and his Article if you read Japanese).
  2. 2Name one end-to-end owner — the Chief of Staff. Paste his five-line description (quoted on this page). CoS does not do the work: dispatch + stop line only.
  3. 3On the shared computer, hand off finished artifacts under /workspace/<project-name>/. Do not paste the work through chat.
  4. 4Human-only login handoff: password/passkey, 2FA, CAPTCHA, payment/KYC, or a site that demands a human. The bot stops and returns those to you.
  5. 5Approval fence: send / purchase / delete / publish / production change. Those wait for your yes.
  6. 6Add a specialist seat only when a stable specialist role appears (the stuck signal).
  7. 7Run a skill once by hand. If it works, save it as a skill, then hang the routine.

Approval fence

Do not send, purchase, delete, publish, or change production without your yes.

What to tweak

Owner seat first. Specialists only on a stuck signal. Humans only on login handoff and the irreversible five.

Source

まどさん @madogiwacowork · Original post

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

Browse templates

Browse team blueprints