SpaceXAI publishes official playbooks for running a Grok Bot team
SpaceXAI released playbooks for operating a Grok Bot team, and the author highlights six roles worth reading first, covering engineering, design, mobile, and product workflows and handoffs.
holy sh*t, SpaceXAI published the playbooks for running your own Grok Bot team. I picked 6 worth opening first. Real roles, workflows, and handoffs from people using the product to get work done. 1/ Engineering → Lingxi Li's domain bots manage Cursor Cloud Agents, inspect PR screenshots, and keep a Notion board of CI failures, conflicts, and review state. 2/ Multiple teams → Eric Zakariasson's experimental setup gives each project a channel, a roster, and a Notion board. Existing bots get reused before new ones are created. 3/ Design → John Bai's bots build interactive prototypes, tune motion using actual production assets, and handle repetitive Figma work through MCP. 4/ Mobile apps → Ryan Perry's six-bot studio connects analytics, creative, engineering, releases, infrastructure, and bug fixes around one game. 5/ Product → Kevin Niparko uses an attention list, an engineering manager, analysts, and a PM bot to turn scattered context into work his team can ship. 6/ Everyday work → Josh Kim's Inbox Manager, Calendar EA, and Intel Scout report through one Bot Boss. One place to catch the decisions that need you. My starting point would be the engineering guide: one domain bot, one feature, screenshot proof, and a reviewable result. Add another specialist when the handoff has a clear job. The latest October 7 update also adds slide decks delivered as PowerPoint or Google Slides. Pick one playbook, connect the needed tools, and teach one repeatable workflow. Keep approval for sends, spending, and destructive actions. The Grok Bot playbook map ↓
This post quotes another post: x.com/unicodef1wn/status/2102375891875581966