handofflisted

Write the note that lets someone else — or a later session — resume work in progress without re-deriving it. Load when context is running out, when pausing unfinished work, when switching who or what continues it, and when asked where things stand. Records tree state, evidence, the next concrete action, and the dead ends. Not a summary of what you did.
sebastienrousseau/agtmls · ★ 1 · AI & Automation · score 80

Install: claude install-skill sebastienrousseau/agtmls

# Handoff **Trigger.** Work is unfinished and continuity is about to break: context is running out, the session is ending, someone else is taking over, you are parking a branch, or a human asked *where are we with this?* > **Reference material** (the template, worked good/bad handoffs, and what to > capture for long-running or multi-agent work): see `reference.md` in this > directory. ## The rule > **A handoff is judged by one thing: can the reader take the next action > without asking you a question?** Not by how much it covers. A handoff that narrates three hours of work and leaves the reader unsure which command to run has failed; four lines that name the next command have succeeded. The default failure is writing a **diary** instead of a **state report**. "First I looked at the parser, then I tried adding a guard, then I realised…" is your experience. The reader needs where things *are*, not how they got there — except where the journey contains traps (see below). ## What a handoff must contain Six parts. Omit any and the reader has to reconstruct it. ### 1. Goal One sentence, in terms of the observable outcome. Not the ticket title — what "done" looks like. ### 2. State of the tree The part people forget, and the one that costs the most when missing: - Branch name, and what it is based on. - Uncommitted changes — and whether they are coherent or mid-edit. - Anything half-applied: a partial migration, a rename stopped halfway, a dependency bumped but not re