handoverlisted

# Handover Produce a compact, structured summary so a fresh agent or session can continue without re-deriving what already happened. This is a **context-handover artifact**, not a status report — the audience is the next agent, not a stakeholder. Save to the temporary directory of the user's OS, not the current workspace. ## When to invoke - 5-10% of the session limit remains with work unfinished: pause at the next safe point and write the handover — don't run to the last token and stop silently. - Context usage passes 40% of the window on unfinished multi-step work. - Context is about to cross an agent, session, or clear boundary — including when the user signals they're about to clear context — or work is blocked and non-obvious state must be preserved. - User says "handoff", "handover", "wrap up session", or a near-equivalent. Skip it when ample context remains and work is progressing, or when the work is complete and legible from the issue, PR, and tests. ## How to produce it 1. Review the full conversation, not just the last few turns — handovers miss things when they only look at recent context. 2. Pull state from these sources, in order: - Any plan file referenced this session. - Task/todo list state — anything in progress or pending. - Background processes started this session — their IDs are load-bearing; the next agent can't rediscover them. - Files created or modified this session — you already know what you touched, don't re-grep to rediscover it