handoff

handoff

Mid-work session continuation handoff.

Write Mode

Triggered by "寫 handoff", "寫 handover", "ctx 太滿", "context 快滿", "clear session 後繼續", "write a handoff", or "hand off to the next session".

1. Collect State Mechanically: Run commands to collect context:

   git branch --show-current
   git log --oneline -5
   git status --porcelain | head -20
   git stash list | head -3
   ls docs/projects/ | grep -v _archive | head
   # Also check open task list if the harness shows one
   

2. Determine Handoff Path:

   • Active project: docs/projects/<project>/HANDOFF.md
   • No project structure: docs/HANDOFF.md
   • Repo not writable or no repo: ~/.autopilot/handoff-manual/<repo-or-cwd-name>.md

3. Generate Document: If HANDOFF.md already exists, REPLACE it (a handoff is a snapshot, not a log) and note the replacement in the reply. Write verbatim:

   ## 目標
   [One-sentence goal of the interrupted work]
   
   ## 現況
   [Branch, last commit SHA+subject, dirty files, what is DONE vs IN-FLIGHT]
   
   ## 已決事項(不重議)
   - [Decision 1] — [One-line rationale]
   - [Decision 2] — [One-line rationale]
   
   ## 下一步
   1. [CONCRETE command or file edit to start with]
   2. [Subsequent concrete step]
   
   ## 驗證方式
   [Commands and expected output proving work is done]
   
   ## Read-order
   1. /absolute/path/to/file1 — [Why to read first]
   2. /absolute/path/to/file2 — [Why to read second]
   3. /absolute/path/to/file3 — [Why to read third]
   
   ## 陷阱
   - [Gotchas discovered this session that would burn the next session]
   

3.5. Route the durable content out (a handoff is a snapshot and gets deleted — Resume Mode step 5. Anything left only in it is scheduled for destruction):

Walk the document you just wrote 段-by-段 and ask of each one:

「這條超出本次交接嗎?」

A 段 that is only true of this interruption (current branch, in-flight diff, the next command) stays in HANDOFF.md and dies with it — correct. A 段 that would still be worth knowing on a different task is durable content sitting in a temporary file, and must be routed now, per the destination table in references/knowledge-routing.md §3: