Back to Details

ds-catchup

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

ds-catchup

ds-catchup

Bring the user back up to speed in a minute, and hand them every call only they can make.
让用户在一分钟内了解最新进展，并把只有用户能做的每个决策交给他。

Steps

Steps

  1. Keep this turn read-only. Do not change code, start jobs or post anything.
  2. Collect what happened since the user's last message: your own work, subagent reports, and messages from others. Tool notifications are not user messages.
  3. Check the current state of anything touched: tests, branches, PRs, running jobs. Use fresh command output, not memory. Fix any number that does not match the source and say you fixed it.
  4. Write what changed in under 100 words. Say what it means for the user, for example "the login bug is fixed and its test passes". Leave out hashes, paths and commands unless the user needs one to act.
  5. List decisions waiting on the user. A decision is something only they can do: a product choice, an approval, an irreversible action, or access you lack. Include old ones still open. For each give: what it changes, the evidence, the risk, your recommendation, and "unknown" for missing facts.
  6. If nothing waits on them, say so plainly.
  1. 本轮保持只读。不要修改代码、启动任务或发布任何内容。
  2. 收集用户上一条消息之后发生的事：你自己的工作、subagent 报告，以及其他人的消息。工具通知不算作用户消息。
  3. 检查所有涉及内容的当前状态：测试、分支、PR、正在运行的任务。使用最新的命令输出，不要依赖记忆。如果某个数字与源内容不一致，则修正该数字并说明已修正。
  4. 用少于 100 字说明发生了什么。说明这对用户意味着什么，例如“登录缺陷已修复，并且其测试已通过”。除非用户需要据此采取行动，否则不要提及哈希值、路径和命令。
  5. 列出等待用户决定的事项。决策是指只有用户能做的事：产品选择、审批、不可逆操作，或你缺少的访问权限。包括仍未解决的历史事项。每项都应给出：它会改变什么、相关证据、风险、你的建议；对于缺失的信息写“unknown”。
  6. 如果没有事项在等待用户决定，直接说明。

Stop when

Stop when

  • The catch-up and the decision list are written. One reply, no follow-up work.
  • 完成回顾总结和决策列表。只回复一次，不要继续后续工作。

Rules

Rules

  • Never invent a decision to fill the list.
  • Work you can still do yourself is not a decision for the user.
  • Name things the way the user would, not by internal labels.
  • Short sentences, no jargon.
  • 绝不编造决策来凑满列表。
  • 你自己仍能完成的工作不属于用户的决策事项。
  • 使用用户会使用的名称来称呼事物，不要使用内部标签。
  • 句子简短，不使用行话。