handofflisted

# Session Handoff Skill Create a structured markdown document that enables a fresh Claude conversation to continue the current task seamlessly. The handoff captures working state — goals, progress, decisions, context, and next steps — so the receiving session picks up exactly where this one left off. ## When to Use - The user explicitly requests a handoff or handover document - The user signals they are stopping now and want to continue the work in a later conversation - Before ending a long or complex conversation with unfinished work - When approaching context limits and needing to start fresh ## Process ### Step 1: Analyse the Session Silently assess: 1. **Work type** — Which category fits? (see Work Type Classification) 2. **Complexity tier** — How deep is the work? (see Depth Sizing) 3. **Active state** — What is the current task, and where exactly did we stop? 4. **Accumulated context** — What knowledge, constraints, and decisions were established that would be costly to re-establish? ### Step 2: Check for User Instructions If the user included specific instructions in their handoff request (e.g. "create a handoff, make sure to include X"), incorporate those. ### Step 3: Clarify Ambiguities (Conditional) **Skip this step entirely if the session state is clear.** Ask **at most 2-3 short, specific questions** only when a genuine ambiguity would produce a materially different handoff: - **Scope** — The session covered multiple distinct topics and it is unclear