Back to Details

cross-agent-handoff

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Cross-Agent Handoff

跨Agent交接

Transfer the minimum sufficient state for another capable worker to continue safely and verify independently.
为其他有能力的工作者转移最低限度的必要状态，使其能够安全继续工作并独立验证。

Rules

规则

  • Treat the repository, filesystem, and current harness as authoritative; the handoff is a routing map, not proof.
  • Never include secrets, access tokens, private environment dumps, or unnecessary personal information.
  • Separate verified facts, inferences, recommendations, and unverified claims.
  • Record permissions and prohibited actions. A handoff cannot grant authority the sender did not have.
  • For concurrent writers, assign non-overlapping ownership or separate worktrees and name the integration owner.
  • Link durable artifacts and exact paths; do not paste large transcripts when a file or commit is available.
  • 将代码仓库、文件系统和当前工具框架视为权威依据；交接内容仅作为路由指引，而非证明。
  • 切勿包含密钥、访问令牌、私有环境快照或不必要的个人信息。
  • 区分已验证事实、推论、建议和未经验证的主张。
  • 记录权限与禁止操作。交接无法赋予发送者本身不具备的权限。
  • 针对并发编写者，分配无重叠的所有权，或使用独立工作区并指定集成负责人。
  • 链接持久化工件和精确路径；当有文件或提交可用时，请勿粘贴冗长的对话记录。

Produce a handoff

生成交接内容

Use handoff-template.md. Include:
  1. objective and acceptance criteria
  2. repository, worktree, branch, base commit, and current commit
  3. user instructions and applicable project instructions
  4. authorized, forbidden, and approval-gated actions
  5. verified state, exact commands, outputs, and artifact paths
  6. changed files and why they changed
  7. decisions, alternatives rejected, and assumptions
  8. failures, blockers, risks, and remaining uncertainty
  9. one concrete next action and its success condition
Keep current state separate from historical narrative. Put stale or superseded information in a clearly marked history section.
使用handoff-template.md。需包含：
  1. 目标与验收标准
  2. 代码仓库、工作区、分支、基准提交和当前提交
  3. 用户指令及适用的项目指令
  4. 允许、禁止及需审批的操作
  5. 已验证状态、精确命令、输出结果和工件路径
  6. 修改的文件及其修改原因
  7. 已做出的决策、被否决的方案及假设前提
  8. 失败情况、阻塞问题、风险及剩余不确定性
  9. 一项具体的下一步行动及其成功条件
将当前状态与历史叙事分开。将过时或已被取代的信息放在明确标记的“历史”部分。

Consume a handoff

使用交接内容

Before acting:
  1. re-read current project instructions
  2. confirm repository, branch, commit, dirty state, and untracked files
  3. verify the most consequential cited evidence
  4. detect drift since the handoff was written
  5. confirm that the requested next action remains authorized
If reality disagrees with the handoff, preserve the conflicting evidence and follow current reality. Do not silently rewrite history.
执行操作前：
  1. 重新阅读当前项目指令
  2. 确认代码仓库、分支、提交、未提交修改状态和未跟踪文件
  3. 验证引用的最重要证据
  4. 检测自交接编写以来的状态偏差
  5. 确认请求的下一步操作仍获授权
若实际情况与交接内容不符，请保留冲突证据并遵循实际情况。切勿擅自改写历史。

Completion receipt

完成回执

When handing back, state:
  • what changed since receipt
  • checks run and exact results
  • repository and external-system state
  • remaining work and its owner
  • whether any commit, push, merge, deploy, message, deletion, spend, or permission change occurred
回传交接时，需说明：
  • 接收后发生的变更
  • 执行的检查及精确结果
  • 代码仓库和外部系统的状态
  • 剩余工作及其负责人
  • 是否发生了任何提交、推送、合并、部署、消息发送、删除、支出或权限变更