/relay

The session ends; the work does not. /relay compresses everything the next agent needs into one document written for a cold start — no shared memory, no session transcript, just the state of the world and the way forward.

Preconditions

1. There is work mid-flow worth continuing — an unfinished ticket queue, a half-settled design, an investigation with open ends. A finished session needs /debrief, not a relay.
2. The next agent is assumed to start cold: everything it needs must be in the document or reachable by a pointer in it.

Write the handoff

The document lands at .scratch/relay/<date>-<slug>.md, in this order:

1. State — what exists right now: branches, commits, open tracker items, files in flight. Facts with pointers, not narrative.
2. Decisions, with why — every decision this session settled and the reasoning that was load-bearing; cite ADRs and glossary entries rather than restating them, and name anything deliberately rejected.
3. Open edges — what is unfinished, each with what blocks it and what proof would close it.
4. Next moves — ordered, each one startable from this document alone.
5. Pointers — issues, commits, files, reports; everything the successor would otherwise have to rediscover.