handofflisted

Use this when the lead session has gotten heavy (long-lived, large transcript — see the auto-wake handoff nudge) and the healthy move is a fresh context, not more of this one. **First, write the handoff file** — a short packet-file-style summary under `~/.relay-tasks/` (gate-exempt), covering: what's in flight, what's reviewed/committed, open questions, next steps. Write it like a memo to your successor, not a transcript dump. Carry forward every `[discipline]` marker your own predecessor's doc had (relay warns if one goes missing — see the linter note below), and on every queue item name an EXECUTOR to do it (or write "delegate this") — never phrase box/deploy/ops work as this lead's own to pick up (§10's `[ops-not-lead-work]` incident: a dropped marker plus ops phrased as the lead's task is exactly how a successor drifted into implementation). **Then run:** ``` ${CLAUDE_PLUGIN_ROOT}/bin/relay handoff <path-to-handoff.md> ``` Call relay as `${CLAUDE_PLUGIN_ROOT}/bin/relay` (Claude Code substitutes the plugin's absolute path when this skill loads) — not bare `relay`, which often isn't on the Bash tool's non-interactive PATH. Unlike other relay commands, handoff reads the caller's session id from `$CLAUDE_CODE_SESSION_ID` automatically — no need to pass it yourself. This opens a NEW lead tab, pre-armed (its routing gate and auto-wake are already active from turn one), seeded with a short pointer at a relay-prepared copy of the handoff file — your source md is never modifi