handofflisted

# Handoff Treat a handoff as a bounded state transfer, not a project report. Give the next agent the current decision, the evidence that makes it true, the safe first action, and the boundaries that prevent duplicate or contradictory work. ## 1. Establish the transfer Identify the recipient and the job they are taking over. State whether the handoff is for a fresh agent, a later session, or a human decision. Record the user's latest intent in their words where possible. Separate it from earlier superseded requests. Finish when the receiving job is explicit and no longer depends on conversation archaeology. ## 2. Re-ground volatile state Verify facts that may have changed: active agents and claims, issue or PR state, branch/worktree status, uncommitted files, and the latest rendered or test result. Do not carry forward status from memory. Capture only artifacts the recipient needs, with exact paths or canonical issue/PR links. Mark each as committed, uncommitted, remote, local-only, retired, or merely referenced. Do not present an unpushed link as available work. Finish when each material claim has a source the recipient can inspect. ## 3. Preserve decisions and boundaries Write the settled decisions first. For each one, name its owner or source of truth and the consequence for the next agent. Then record unresolved decisions as choices, not as accidental assumptions. If an ordering, authorization, product meaning, or dependency is genuinely undecided, make the fir