handofflisted

# Handoff — write it, delegate it, monitor it A handoff **ends this session's ownership of the work**. Three phases, in order: write the document, launch a successor session that continues the work in its own context window, then stay on as its monitor. This session does not carry on building — it watches, integrates, and lands. **Delegation is the default, not a follow-up step.** A handoff that stops at a written document leaves the work in the context window it was written to escape, and the second step (`/relay`) is the one nobody takes. The single documented exception is [Document only](#document-only) below. One successor is this skill. A coordinated fleet — several workers, per-worker branches, waves — is the `successor` skill (ADR-0059). Both launch through the same script and inherit its refusals; neither re-implements them. --- ## 1. Write the document `.claude/.runtime/handoff/<ISO8601>.md` — e.g. `.claude/.runtime/handoff/2026-07-09T13-04-22Z.md` (colons are not path-safe on every filesystem; use `-` in the time portion). `.claude/.runtime/` is git-ignored and is the established home for harness-internal session state, so the handoff survives an OS temp sweep, stays out of every commit, and never reaches a remote. Create the `handoff/` directory if absent. Do not write to the OS temp directory, and do not write anywhere else in the workspace. Copy this skeleton and fill it in: ```handoff-skeleton --- created_at: 2026-07-09T13:04:22Z project_id: odin mem_cl