抄作业 / 教程 / Grok Bot
Department Grok Bot Playbook — 23-role IT roster
标题与摘要为原文，未翻译。
- 做了什么
- MIT documentation-only playbook for running Grok Bot like a governed IT department: 23 roles, charter, economy mode, and yes/no/hold gates.
- 场景
- 未归类
- 资料完整度
- 作者与原链接有
- 做了什么有
- 来源原文摘录有
- 截图 / 媒体来源未提供
- 步骤 / 章节有
- 提示词 / 配置原文来源未提供
- 结果 / 数字来源未提供
- 风险提示有
- 相关条目有
— 表示来源没有给出，本站不补写。
- 来源原文摘录
[](LICENSE) [](docs/01-why-this-matters.md) [](roster/README.md) [](docs/04-operating-charter.md) [](docs/06-economy-mode.md) [](#disclaimer)
RongleCat/awesome-grok-bot (GitHub) · 打开原文 ↗ 摘自项目 README，照录原文，未翻译。
- 来源里的步骤 / 要点
- Read Why this matters and the operating charter. Internalize drafted ≠ executed ≠ verified.
- Sketch your fleet from the architecture and roster index. Start with Orchestration Agent plus three specialists, not twenty-three.
- Create one Bot per role using the agent profile and orchestration profile templates. Paste the matching file from roster/ as standing instructions.
- Connect durable API / MCP access (tickets, identity, cloud). Do not paste secrets into chat. See secrets and access.
- Turn on economy mode and the economy-mode rules. Batch gates. Ban auto follow-on spam.
- Run one sample workflow in draft-only mode. A human must yes before anything executes.
- Only then follow the implementation guide for Super Grok / Grok Bot rollout.
- Orchestration lead. One Orchestration Agent is the front door. Specialists do not freelance across lanes.
照录来源原文，未翻译。
- 提示词
来源没有给出可直接复制的提示词原文。
- 怎么复制
- 打开仓库：github.com/ericbrianpearson/department-grok-bot-playbook ↗
- 读 README，把仓库链接发给你的 Bot，让它按 README 复现
- 先在小范围跑通，再加 routine
- 风险与限制
- 涉及付款、下单或预订：先让 Bot 只起草，确认后再执行
- 作者的结果不保证能复现，以原帖为准
- 用量预估
- 用金属计算器估一下