handoff

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save to the temporary directory of the user's OS - not the current workspace.

Include a "suggested skills" section in the document, which suggests skills that the agent should invoke.

When the facts are available, include a compact Continuation section with:

the exact source task ID (omit it rather than guessing),
the current execution owner (
```
source
```
,
```
receiver
```
, or
```
unassigned
```
),
the repository, branch, fixed point, and worktree state when relevant.

If the source and receiving sessions are existing Codex App tasks working in the same directory, suggest

/codex-task-messenger

. The receiver may use it to ask the source task one concrete question when the answer is not settled by the handoff or its referenced artifacts. A Messenger reply supplements the handoff; it does not replace the handoff or expand the user's authorization.

Before editing a shared directory, the receiver should confirm execution ownership once if the handoff leaves it unclear. Read-only clarification does not require an ownership transfer. If the source task is unavailable or Messenger is incompatible with the destination, continue from the handoff and referenced artifacts, surfacing only a real blocker.

Do not duplicate content already captured in other artifacts (specs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead.

Redact any sensitive information, such as API keys, passwords, or personally identifiable information.

If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.

撰写一份总结当前对话的交接文档，以便新的Agent可以继续开展工作。将文档保存到用户操作系统的临时目录中——而非当前工作区。

在文档中加入「推荐技能」板块，列出Agent应调用的技能。

当相关信息可用时，加入简洁的续接板块，包含：

准确的源任务ID（若不确定则省略），
当前执行所有者（
```
source
```
、
```
receiver
```
或
```
unassigned
```
），
相关的仓库、分支、固定点和工作树状态。

如果源会话和接收会话是在同一目录下运行的现有Codex App任务，建议使用

/codex-task-messenger

。当交接文档或其引用的工件无法给出明确答案时，接收方可以通过它向源任务提出一个具体问题。Messenger的回复是对交接文档的补充；它不会替代交接文档，也不会扩大用户的授权范围。

在编辑共享目录之前，如果交接文档未明确执行所有权，接收方应确认一次执行所有权。只读性质的澄清不需要进行所有权转移。如果源任务不可用，或者Messenger与目标环境不兼容，则根据交接文档和引用的工件继续工作，仅在遇到实际障碍时才提出问题。

不要重复其他工件（规格说明、计划、ADR、问题、提交记录、差异文件）中已包含的内容。而是通过路径或URL引用它们。

编辑掉任何敏感信息，例如API密钥、密码或个人身份信息。

如果用户传入了参数，则将其视为下一会话重点内容的描述，并据此调整文档。