返回详情页

catchup

对比查看原文与翻译

🇺🇸

原文

英文
🇨🇳

翻译

中文
Catch the human up at their eye level, from state, not from memory.
以用户的视角，基于项目状态而非记忆，帮助他们快速跟上进度。

Goal

目标

catchup
is the re-entry point for a lost human. Long agent cycles coin words, rename files, run experiments, and make calls faster than the owner can follow. Before any next action makes sense, the owner's mental model must be reloaded. 
catchup
reads the live project state and returns a briefing a person with zero retained context can act on. It runs before the next move gets decided: catchup restores the map, so that decision starts from truth instead of a stale memory of it.
catchup
是帮助回归项目的用户重新融入的切入点。Agent的长期运行会创造新术语、重命名文件、开展实验并进行操作，其速度远超项目所有者的跟进速度。在采取任何合理的下一步行动之前，必须更新项目所有者的认知模型。
catchup
读取项目实时状态，并生成一份简报，即使是完全丢失上下文的用户也能据此采取行动。它会在决定下一步行动前运行：
catchup
重建项目认知地图，让决策基于真实状态而非过时的记忆。

Workflow

工作流程

  1. Read live state only: recent file mtimes, git log/diffs, plan and state docs, re0-memo notes, task boards. Never brief from conversation memory alone — memory is what drifted.
  2. Anchor on the human's last touch (their last message, judgment, or commit). Everything after that point is the delta; everything before it is assumed known and stays out.
  3. Compose in decision order, not chronological order:
    • Needs you — decisions, judgments, or inputs only the human can give, each self-contained enough to act on without opening another file.
    • Changed while you were away — outcomes, not process. "The plan's scoring rule was replaced" beats "I ran three analysis passes."
    • New words — every term coined or repurposed since their last touch, one line each, with where it lives. Skip terms they already used themselves.
  4. Gloss on first use: any project-specific term appearing in the briefing gets an inline plain-language aside at its first occurrence, even if a glossary section follows.
  5. Keep the default short (a screen or less). End with drill-down offers per section, not with everything expanded.
  1. 仅读取实时状态：最近的文件mtimes、git log/diffs、计划与状态文档、re0-memo笔记、任务看板。绝对不要仅基于对话记忆生成简报——记忆已经过时。
  2. 以用户的最后操作（最后一条消息、判断或提交记录）为锚点。该时间点之后的所有内容为变更增量；之前的内容默认用户已知，无需提及。
  3. 按决策优先级而非时间顺序组织内容：
    • 需要您参与 —— 仅需用户做出的决策、判断或输入，每项内容需足够独立，无需打开其他文件即可采取行动。
    • 您离开期间的变更 —— 聚焦结果而非过程。例如，表述为“计划的评分规则已替换”优于“我执行了三次分析”。
    • 新术语 —— 用户最后操作后创造或重新定义的所有术语，每项一行，并标注其出处。跳过用户自己曾使用过的术语。
  4. 首次出现时解释：简报中出现的任何项目特定术语，在首次出现时需附带通俗易懂的 inline 解释，即使后续有术语表部分。
  5. 默认保持简洁（不超过一屏内容）。结尾按板块提供深入查看选项，而非直接展示全部扩展内容。

Rules

规则

  • State-grounded: every claim traces to a file, commit, or artifact the human can open. No "as we discussed."
  • Read-only on the project. 
    catchup
    briefs; it does not fix, rename, or decide.
  • The ask comes first. A briefing that buries the one question needing the human is a log.
  • Outcome voice, not journey voice. Narrating the agent's process is self-report, not briefing.
  • Silence the settled: closed decisions and healthy metrics get one line or none.
  • Honest completeness: "done" means verified done; "moved" is not "reconciled"; say which.
  • Do not re-explain terms the human demonstrably knows (they used them first).
  • 基于状态：每一项陈述都可追溯至用户能打开的文件、提交记录或工件。禁止使用“如我们之前讨论的”这类表述。
  • 对项目只读：
    catchup
    仅提供简报；不进行修复、重命名或决策操作。
  • 需求优先：将需要用户处理的问题放在最前面。把用户需关注的问题隐藏在简报深处的内容只是日志，而非有效简报。
  • 结果导向，而非过程导向：叙述Agent的运行过程属于自我汇报，而非简报内容。
  • 省略已解决事项：已完成的决策和正常的指标只需一行描述或完全省略。
  • 诚实完整：“完成”指已验证完成；“已移动”不等于“已协调”；需明确说明状态。
  • 无需重复解释用户已知的术语（用户曾率先使用过的术语）。

Verification

验证

Before finishing:
  1. Cold-read the briefing: no sentence requires pre-gap memory or an unglossed coined term to parse.
  2. The "needs you" items are each actionable without opening another file.
  3. Every claim has a checkable source (file, commit, artifact path).
  4. It fits on a screen, with expansion offered rather than delivered.
完成前需检查：
  1. 通读简报：所有语句无需依赖间隔前的记忆或未解释的新术语即可理解。
  2. “需要您参与”的每项内容无需打开其他文件即可采取行动。
  3. 每一项陈述都有可核查的来源（文件、提交记录或工件路径）。
  4. 内容不超过一屏，提供扩展选项而非直接展示全部内容。