handoff

Move in-progress work from one agent to the next — a different session, a different machine, a different day — through a structured document committed to the repo. Two directions, one skill: write a handoff, or resume one.

The document is the whole product. It is written for a reader who has none of the writer's session — no scrollback, no open files, no memory of what was already tried. A handoff that only makes sense to the agent that wrote it has failed at the one job it has.

Workflow

1. Route

Situation	Action
Work is in flight and must be parked or passed on	Write — steps 2–5
A handoff exists and the user wants to continue it (`0003`, "resume")	Resume — steps 6–8
Work was resumed but is unfinished and is being parked again	Update in place — step 9

2. Make the work reachable — before writing anything

A handoff is committed so another machine can pick it up. That promise is only kept if the work travels too, not just the note about it.