Build a Handoff-Capable Robot Squad with Grok Bot: Role Map, Pipeline, and Six-Category Ask-First Checklist

Input: your actual workflow and recurring tasks → Process: use Grok Bot to generate a named-role bot squad configuration → Output: role map, shared directory conventions, pipeline rules, and self-check checklist

Who

Operators, creators, or small-team leads who want AI chat windows to work as a pipeline instead of chaotic parallel threads

You get

A named-role map, shared directory convention, coordination protocol, inventory role, and six-category ask-first checklist

You need

Grok Bot

Steps

1. Define the Coordinator Role

   Define a 'Coordinator' in your Bot as the dispatch/coordination/deployment-rollback entry point. Clarify it does not approve compliance releases or write final drafts for specialists. Send the goal prompt to Grok Bot.

   Setup guidance · Source text。Grok Bot conversation starter

   Copy prompt

   目标：搭一个能点名分工、能交班、能把关、能打扫的小队，而不是开一堆互不理睬的聊天窗口。

2. Split Specialist Roles

   Split roles by work you actually repeat. For each role, write its real name, one-sentence duty, input/output directories, and prohibitions (no publishing, no logging into others' accounts, no reading keys).

3. Create Shared Directories

   Create and name shared directories in order: 00-profile (style/role rules) → 01-inbox (raw material and story cards) → 02-briefs (story briefs, valid only after your personal approval) → 03-drafts → 04-review → 05-published (draft / reviewed / archived after you publish). Names are customizable; sequence must be preserved.

4. Lock the Pipeline Rules

   Set and enforce the pipeline: material enters inbox → you approve brief → writer drafts only from brief → fact-checker verifies hard facts → compliance approves before layout → you publish. Halt at any step marked 'do not ship.'

5. Open the Coordination Channel

   Append three coordination topics to each role's instructions: human instructions relayed via coordinator, status checks on specific orders, and shared rule updates. Beyond this, specialists report to you and the editor-in-chief (or designated lead), preventing everyone from shouting across channels.

6. Add an Inventory Role

   (Can be added later.) Set a read-only inventory role (example name: Agent Smith): observe by default; changing descriptions, deleting files, moving routines, or editing shared memory requires your named approval. Do not wake the whole fleet just to clean house.

7. (Optional) Team Roster Dashboard

   Read-only pull of each bot's on-duty status, refreshed on a schedule. External sharing excludes the roster by default. Without a ready dashboard tool, start with a simple table: Role | One-line duty | Last updated.

目标：搭一个能点名分工、能交班、能把关、能打扫的小队，而不是开一堆互不理睬的聊天窗口。

【你将得到】
- 一张可点名的岗位图（名字可自定；逻辑是分工）。示例分组：
  - 调度：总管（只调度/协调/部署回滚入口，不替专职岗写终稿）
  - 编辑部流水线：私人主编、私人素材官、私人主笔、私人校准官、私人合规官、私人排版官
  - 清点：Agent Smith（只读清点，先观察→请示→再改）
  - 专项岗示例：财务经理、独立调查员、制图工作室、动效工作室、即梦、Minmax、头像角色设定图、CoreS3 技术栈、二蛋、传输/域名/vps、godaddy、pi agent、K3学习；归档岗如 x运营 标明不再接新派单
- 1 套共享目录约定（inbox → brief → draft → review → published）
- 1 条协调口子（专职岗什么时候可以找总管）
- 1 张「六类先问」清单（迁移、部署、花钱、改权限、对外发消息、删东西）
- （可选、非主菜）一页「谁在岗」只读看板的产品意图——有现成工具再用，没有就先用表格

【怎么做 · 最小步骤】
1. 先写「总管」说明：只调度、拆需求、协调；不替合规放行、不替主笔写终稿。
2. 按你真会重复做的活拆岗，并写上真名职责一句。每岗写清：输入、输出目录、禁止项（不发布、不登录别人账号、不读密钥）。
3. 建共享目录（名字可自定，逻辑保持顺序）：
   - 00-profile：文风、角色规矩（人改，bot 不擅自放宽硬边界）
   - 01-inbox：素材与选题卡（未批准 ≠ 可写）
   - 02-briefs：选题 Brief（须你本人批准才算数）
   - 03-drafts → 04-review → 05-published：初稿 / 审过 / 你发布后的存档
4. 钉死流水线：素材进 inbox → 人批准 Brief → 主笔只按 Brief 写 → 校准核硬事实 → 合规把关通过才能排版 → 人发布。任一步「不可发」就停。
5. 开「协调口子」（三类事写进各岗说明末尾）：
   - 人经由总管转达的指令
   - 协调查某单状态
   - 共同规则同步
   除此之外专职岗仍对你和主编（或指定编辑负责人）汇报，避免全员互相喊话。
6. 加清点岗（可后加，示例名 Agent Smith）：默认只读；改描述、删文件、动例程、改共享记忆必须你点名批准；清点轮不要为了打扫吵醒整支舰队。
7. （可选）「员工页」产品意图：只读拉取各 bot 在岗状态，定时刷新；对外分享默认不带员工页。没有现成大屏就先用一张表：角色｜职责一句｜最后更新日。