Back to Details

write-handoff

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Write Handoff

撰写交接文档

Give the next worker enough stable context to complete one bounded job without recreating the owning Plan or docs.
Use workflow-language.md, review-language.md for review work, and handoff-template.md.
为后续工作人员提供足够的稳定上下文，使其无需重新梳理所属计划或文档即可完成一项有限范围任务。
撰写评审相关工作时，请参考workflow-language.md、review-language.md，并使用handoff-template.md模板。

Choose intent and lifecycle

选择任务目标与生命周期

Common types are implementation/continuation, research, refactor/bugfix, review, review-continuation, and review-fix. Use the smallest type that describes the next job.
Choose lifecycle from expected use:
  • Immediate: next known worker or near-term continuation; current paths and volatile status may help.
  • Durable: later or unknown worker, or reusable work across tools; emphasize stable behavior, acceptance criteria, and scope boundaries.
Default to Immediate unless the expected lifecycle clearly requires Durable. A handoff in chat or a file can be either; file storage does not imply durability.
常见的任务类型包括：功能实现/延续开发、研究调研、重构/Bug修复、评审、评审延续、评审修复。请选择最贴合后续任务的最小粒度类型。
根据预期使用场景选择生命周期：
  • 即时型：面向已知的后续工作人员或短期延续任务；可提供当前路径和临时状态信息以提供帮助。
  • 持久型：面向后续未知工作人员，或可跨工具复用的工作；重点强调稳定行为、验收标准和范围边界。
除非预期生命周期明确需要持久型，否则默认使用即时型。聊天或文件中的交接文档都可采用任意一种类型；文件存储并不意味着必须使用持久型。

Build the handoff

构建交接文档

  1. Read the owning Plan, docs, Review Ledger, current diff, or source only as needed for this task.
  2. State the exact task, current state, scope, constraints, completion conditions, and verification.
  3. Link only authoritative files the next worker actually needs. Do not copy whole Plans/docs or generate a replacement Plan.
  4. Include volatile implementation notes only when they are not discoverable and materially reduce rework.
  5. Keep adjacent ideas out of scope or in the owning Plan's follow-ups.
Create a file only when the user asks for one or the authorized workflow clearly needs a stored artifact. Use the repository's established handoff location when present; otherwise ask or return copyable text.
  1. 仅根据当前任务需求，阅读所属计划、文档、评审台账、当前差异或源代码。
  2. 明确说明具体任务、当前状态、范围、约束条件、完成标准和验证方式。
  3. 仅链接后续工作人员实际需要的权威文件。请勿复制完整的计划/文档或生成替代计划。
  4. 仅当临时实现说明无法通过其他途径获取且能显著减少重复工作时，才将其纳入。
  5. 将无关的相邻想法排除在当前范围之外，或归入所属计划的后续任务中。
仅当用户明确要求，或经授权的工作流明确需要存储工件时，才创建文件。若仓库已有既定的交接文档存放位置，则使用该位置；否则请询问用户或返回可复制的文本内容。

Review handoffs

评审交接文档

  • For a continuation/delta round, carry accepted findings, patch notes, changed surface, settled items, Review Signal, unresolved risks, and intended next scope.
  • For explicit independent cross-validation, say that overlap is possible and avoid anchoring the reviewer to desired findings.
  • If 
    fresh review
    could materially mean continuation or independent cross-validation, consolidate that choice with any other owner questions rather than silently choosing.
  • If prior Review Signal was Low, note the likely low return without refusing an explicitly requested round.
  • 对于延续/增量迭代环节，需涵盖已接受的结论、补丁说明、变更内容、已确定事项、评审信号、未解决的风险以及预期的后续范围。
  • 若需进行明确的独立交叉验证，请说明可能存在重叠情况，避免引导评审人员得出预设结论。
  • 若“全新评审”可能同时意味着延续开发或独立交叉验证，请与其他所有者问题一同确认选择，而非自行决定。
  • 若之前的评审信号为低优先级，需注明该环节可能回报较低，但不得拒绝明确要求的评审环节。

Owning artifact updates

所属工件更新

Do not add bookkeeping just because a handoff exists. Update a Plan only when verified Task state, required work, or follow-ups changed. Add a sparse pointer to a handoff file only when it prevents the artifact from being lost.
Use handoff-template.md, omit unused sections, and keep the result self-contained and concise.
请勿仅因存在交接文档就添加记录工作。仅当已验证的任务状态、所需工作或后续任务发生变化时，才更新所属计划。仅当交接文档能防止工件丢失时，才在计划中添加指向该文件的简洁链接。
请使用handoff-template.md模板，省略未使用的章节，确保最终内容独立完整且简洁。