Set up a chief bot and specialist teams that share one workspace

You are helping me set up this AI use case end to end in Claude Code.

Goal: Set up a chief bot and specialist teams that share one workspace
What the original author did: A summary of SpaceXAI's 2-page operator manual for Grok Bot: create a chief first that routes and monitors rather than working, keep research and handoffs in /workspace instead of chat, split content, ops, research and coding into specialist bots, give each workflow a source, evidence and action gate, and have humans approve only money, publishing, deletion, signatures and irreversible actions.
Reported result (as claimed by the author): It also lists costly mistakes: constant polling burns quota and bad retries duplicate actions.
Source: https://x.com/irongiantXBT/status/2113420143959195748
Tools they used: Grok Bot
Category: Automation & business

Please:
1. Ask me 3 short questions about my situation (accounts I have, budget, what I want the output to look like).
2. Propose a step-by-step plan using these tools or cheaper alternatives, with the time and cost of each step. Use official pricing pages; say "check pricing" if unsure.
3. Then do the setup with me one step at a time, waiting for my OK before anything that sends messages, posts publicly, spends money or deletes data.
4. Finish with a checklist to run it again next time.

You are helping me set up this AI use case end to end in Codex.

Goal: Set up a chief bot and specialist teams that share one workspace
What the original author did: A summary of SpaceXAI's 2-page operator manual for Grok Bot: create a chief first that routes and monitors rather than working, keep research and handoffs in /workspace instead of chat, split content, ops, research and coding into specialist bots, give each workflow a source, evidence and action gate, and have humans approve only money, publishing, deletion, signatures and irreversible actions.
Reported result (as claimed by the author): It also lists costly mistakes: constant polling burns quota and bad retries duplicate actions.
Source: https://x.com/irongiantXBT/status/2113420143959195748
Tools they used: Grok Bot
Category: Automation & business

Please:
1. Ask me 3 short questions about my situation (accounts I have, budget, what I want the output to look like).
2. Propose a step-by-step plan using these tools or cheaper alternatives, with the time and cost of each step. Use official pricing pages; say "check pricing" if unsure.
3. Then do the setup with me one step at a time, waiting for my OK before anything that sends messages, posts publicly, spends money or deletes data.
4. Finish with a checklist to run it again next time.

You are helping me set up this AI use case end to end in Grok Bot.

Goal: Set up a chief bot and specialist teams that share one workspace
What the original author did: A summary of SpaceXAI's 2-page operator manual for Grok Bot: create a chief first that routes and monitors rather than working, keep research and handoffs in /workspace instead of chat, split content, ops, research and coding into specialist bots, give each workflow a source, evidence and action gate, and have humans approve only money, publishing, deletion, signatures and irreversible actions.
Reported result (as claimed by the author): It also lists costly mistakes: constant polling burns quota and bad retries duplicate actions.
Source: https://x.com/irongiantXBT/status/2113420143959195748
Tools they used: Grok Bot
Category: Automation & business

Please:
1. Ask me 3 short questions about my situation (accounts I have, budget, what I want the output to look like).
2. Propose a step-by-step plan using these tools or cheaper alternatives, with the time and cost of each step. Use official pricing pages; say "check pricing" if unsure.
3. Then do the setup with me one step at a time, waiting for my OK before anything that sends messages, posts publicly, spends money or deletes data.
4. Finish with a checklist to run it again next time.