session-handofflisted

# session-handoff — passing work between sessions on one machine Hand the work in this session's hands to **another session**, or to **this same person's next session.** **Core principle: the receiver must see "fixed or not fixed?" at first glance.** A handoff is not a work log — it's a status note that lets someone decide the next step **within three lines.** ## When to use - You need to pass live work to another running session, or write it for your own next session. - You're wrapping up and want to leave a "here's where I got to." **Not for:** - **Dispatching subagents / parallel tasks** → that's a parallel-agent dispatch skill. **Handoff ≠ dispatch**: a handoff moves **existing context** to a session that already exists; dispatch **constructs** the context a new agent needs. - **Sending a message to a person** (teammate, boss, engineer) → use an audience-tailored message skill. - **Session timeout / reconnect** — that's a connection problem, not a handoff. --- ## Output 1: `HANDOFF.md` Write to the scratchpad directory by default; `--out <path>` for elsewhere. **Six sections — a missing section is worse than a wrong one:** | Section | What goes in | |---|---| | **What changed** | Per file: absolute path + what changed + why | | **Unfinished** | Which step is missing, what the next step concretely is (not "look into it more") | | **Landmines** | Traps you hit, paths not to retread, inputs known to blow up | | **git snapshot** | See section 2 — all four items, with