handofflisted

# handoff — resume cold, lose nothing A handoff is not a to-do list. It is a **snapshot of reality** precise enough that a fresh agent with no memory of this session can pick up exactly where you left off and make the next correct move. Prefer **state over instructions**: "flag `SF_X` is committed but OFF; flip preconditions are Y" beats "go turn on the flag." State stays true when plans change; instructions rot the moment anything shifts. ## When to use - Ending or pausing a session with unfinished work. - You sense a compaction coming (long session) and want the load-bearing state written down, not summarized away. - Passing a task to another agent, another worktree, or your future self. ## Write these 8 sections (skip one only if truly empty) 1. **Goal** — the one-sentence objective and why it matters; what "done" looks like, observably. 2. **State now** — what is *actually true* this moment: what's built, merged, committed (name the shas + branch), deployed, flagged (on/off), reverted. The load-bearing section. Facts, not narration. 3. **Where it lives** — branch, worktree path, the 3-5 key files/seams, the spec/plan doc, any relevant PR/deploy URL. The map, so the next agent doesn't re-discover it. 4. **Next step** — the single most correct next action, concrete enough to start on, then the 2-3 that follow. Not a full plan — the next move. 5. **Open decisions** — what's genuinely undecided and needs the human, each with the options + your recom