收据式完成、交接便条、Routine 审计：一周改造 Bot 团队的运行闭环
Receipts before 'done', handoff notes and routine audits: one week of tightening a bot team
X, @GetClareity, 2026-11-07
多 Bot 协作 全文核对建议先读
https://x.com/GetClareity/status/2118906689055256905
场景
多 Bot 团队跑定时任务时常出现「以为做完了」、重复读长聊天、用量失控和过多打扰
A multi-bot team running scheduled jobs kept producing false 'done's, re-reading long chats, burning usage and pinging too often
他们怎么做
每次运行结尾必须给证据（每项链接、跳过原因、待我处理清单）；Grok Bot 只当前门路由，Claude 负责键盘前的构建；定期用审计提示词列出全部 Routine 的频率并标 keep/slow/trigger/retire；多步流程按阶段拆给不同 Bot，只有 Chief of Staff 能联系本人；每次运行结束写不超过约十行的状态文件，下次先读它；只读的开支检查提示词
Every run must end with receipts (a link per action, why anything was skipped, what waits on me); Grok Bot is the front door that routes, Claude is where building happens; a routine-audit prompt lists every routine's cadence and marks keep / slow / trigger / retire; multi-stage workflows get one bot per stage and only the Chief of Staff may ping the owner; each run writes a ~10-line status file the next run reads first; a read-only spending-check prompt
可以拿走的做法
复制「闭环」而非 Bot 名单：每步一个负责人；每次运行留交接便条；按计划审计 Routine；只留一个能打扰你的入口，且只为决策打扰
Copy the loop, not the roster: one owner per step; a short handoff note after every run; audit routines on a schedule; one front door that pings you, and only for decisions结果与限度
作者自述做法，无量化数据；没有公开具体工作流名称。
Author's own account with no numbers; the concrete workflow is deliberately not named.
来源
- 平台
- X
- 作者
- @GetClareity
- 日期
- 2026-11-07 11:21 Asia/Taipei (UTC+8)
- 日期依据
- X API created_at 2026-11-07T03:21:36.000Z（X Article）
- 时间窗
- 近7天 案例字段「近7天」相对采集截止 2026-11-11 09:26 Asia/Taipei，不是相对打开页面的今天
- 原分类
- 一手实践/运行规范
这条证据标签是什么意思
全文核对
来源已经读过（帖子、文章或字幕）。这只说明原文被读过，不代表本站复现了作者的结果。
标签不是评分。全文核对只表示来源被读过，不表示结果已被复现。
X API 返回 X Article 全文；做法为作者自述，未复现