handofflisted

# Session handoff You are preparing a handoff: a compact, structured state file that lets a *fresh* session — with none of this conversation's context — continue the work. The reader knows nothing you don't write down. Optimize for what the next session needs to act, not for narrating history. ## Steps 1. Determine the project root (nearest ancestor with `.git`, else cwd) and ensure the directory `.claude/handoff/` exists under it. 2. Write `.claude/handoff/latest.md` with YAML frontmatter and exactly these sections: ```markdown --- created: <ISO-8601 now> source: skill project: <absolute project root> git_branch: <current branch or "unknown"> --- # Session handoff ## Goal / current task <What the user is ultimately trying to achieve, and the specific task in progress right now. 2-5 sentences.> ## State of work <Done / in-flight / blocked, as tight bullets. Include verification state: what's tested, what isn't.> ## Key decisions & constraints <Decisions made this session WITH their reasons, and constraints the next session must not violate. Include approaches that were tried and rejected — that knowledge is expensive to rediscover.> ## Files in play <Bullet list: path — why it matters right now. Only files that matter for continuing.> ## Last exchange <The most recent user request and where you left off answering it, condensed.> ## Next steps <Numbered, concrete, in order. First step should be executable immediately.> ## Open questions <Anything unresolved that th