session-handoff
Installation
SKILL.md
Session Handoff
A handoff is context transplanted, not context summarized. The successor is not a reader being briefed on someone else's work; it IS this session, with a new window. Everything it needs to act must be on disk, addressable, and true at the moment it reads.
The skill is small on purpose. The heavy artifact is the markdown it produces, and the whole contract lives in .agents/skills/session-handoff/references/capture-contract.md.
What this is not
| Looks similar | Actually is | Use |
|---|---|---|
| hand a scoped task to another session and supervise it | orchestration: Task, Dispatch, mailbox, the work comes back | /orca-orchestration |
| hand work away and stop caring | ownership transfer of a TASK, one direction, no return | the binary's own orca-cli guide |
| remember a decision for next month | durable cross-session fact, project-scoped | Engram (mem_save) |
| shrink the window and keep going | harness compaction, lossy, not addressable, not yours to shape | nothing to do |
| hand the whole SESSION to its own successor | this skill | here |
The distinction that matters: compaction keeps what a summarizer judged salient. A handoff keeps what the NEXT actor needs, which is a different set, and it is written by the only party that knows the difference.