handofflisted

# Handoff Skill Your job is to produce a **handoff document** — a compact, self-contained markdown file that a brand-new agent (with zero context from this conversation) can read and immediately continue the work effectively. ## Why this matters Agents lose context across sessions. A good handoff document lets work continue without the incoming agent asking "what are we doing?" or making decisions the current session already resolved. Everything the new agent needs should be in the document; nothing else should be assumed. ## What to extract from the conversation Read the full conversation carefully. Pull out: 1. **Goal** — What the user is ultimately trying to accomplish. One sentence. If the goal shifted during the conversation, note the current goal. 2. **Context** — Project name, directory, tech stack, key constraints, relevant background the user shared. Keep it tight — only what shapes decisions. 3. **What's been done** — Concrete completed actions: files created/edited, commands run, features implemented, PRs opened. Reference specific file paths and line numbers when known. 4. **Key decisions made** — Choices that were discussed and settled. Include the _reason_ — "we chose X because Y" — so the new agent doesn't re-litigate them. 5. **Current state** — Where things stand right now. What's working, what's broken, what's half-done. If there are uncommitted changes or a partial implementation, say so. 6. **Open items / blockers** — What's