handofflisted

# Handoff Write a concise handoff document so a fresh agent can continue from the current state without rereading the whole conversation. ## When to use - User asks for `/handoff`, "handoff this", "handoff to /prototype", "handoff back", "summarize for next session", or "another agent should continue". - A long planning, prototype, diagnosis, or implementation thread is about to switch focus or end. - A side quest should run in another session and return with a compact verdict. ## Process 1. Identify the handoff target. If the user passed arguments, treat them as the next session's focus, such as `/prototype`, `/tdd`, or "back to grilling session". 2. Create `.scratch/handoffs/` if needed. 3. Save the handoff as `.scratch/handoffs/YYYY-MM-DD-<short-slug>.md`. Use the current local date and a slug for the target or topic. If a file already exists, append a short numeric suffix rather than overwriting. 4. Before writing, read any existing file at that path so you do not clobber prior notes. 5. Write only the context the next agent actually needs. ## Content Include: - Goal: what the next session should do. - Current state: what has already been decided or done. - Key unresolved questions. - Relevant artifacts: PRDs, issues, ADRs, design docs, prototype paths, commits, diffs, URLs. - Suggested next skill or command. - Return instructions: what result should come back to this thread or parent skill. Do not duplicate content already captured in PRDs, plans, ADRs, issues,