| name | session-handoff |
| description | Package this session for a fresh chat. Trigger on "summarize this for a new session", "hand this off", "session summary", "transfer this context", "continue this in a new chat", "build a handoff", "wrap this up for next time", "create a prompt for a fresh session", "context transfer", "prepare for handoff", "we've gone deep, let's start fresh", "package this up", or any reference to transferring conversation context to a new session or a different user's Claude. Also fires when Claude detects the conversation is very long and the user mentions starting fresh, continuing later, or sharing context with someone else. Do NOT trigger for simple conversation summaries, meeting prep, or document creation tasks.
|
| why | Makes work transferable to a new session or another person without losing the reasoning behind decisions - context in chat alone is gone the moment the session ends. |
| enhance | Be explicit about handoff type (A/B/C) at the start - the skill strips internal strategy and inlines skill-dependent knowledge differently for each type, and guessing wrong produces a document that leaks or lacks context. |
| allowed-tools | ["Read","Write"] |
| mcp_requirements | [] |
Session Handoff
Runs on: local-writes - creates or edits files in your OS folder; needs an agent with write access.
The goal: the receiving session picks up without re-explaining anything, regardless of whether it has installed skills, memory, or prior context.
Step 1: Identify the Handoff Type
Ask if not obvious from context. The three types require different packaging:
Type A: Same-User Continuation
The same user continuing in a fresh session within the same project. The receiving session has access to all installed skills and project memory.
What to include: Everything. Full context, internal strategy, file locations, skill references.
What to strip: Nothing. This is an internal transfer.
Type B: Cross-User Handoff
Context being passed to a different person's Claude session. The receiving session likely has NO installed skills, NO project memory, and NO prior context.
What to include: Confirmed decisions, deliverable specs, guiding principles (rewritten as standalone directives), file locations they can access, and clear next actions.
What to strip: Internal strategy, pricing rationale, protection caps, advisor involvement, competitive positioning, anything marked as internal-only during the session. Also strip skill references - the receiving session doesn't have them.
What to add: Self-contained context that installed skills would normally provide. If the session used research or calculations, inline the relevant findings and numbers. The handoff must carry the knowledge that skills would otherwise supply.
Type C: Fresh-Session Prompt
A self-contained prompt the user can paste into any Claude session and get useful work immediately.
What to include: Everything needed as a single prompt - context, specs, decisions, constraints, deliverable requirements.
What to strip: Same as Type B, plus any conversational framing. Write as instructions, not as a summary.
Format: Wrap the entire handoff in a prompt structure the receiving Claude can act on immediately.
Step 2: Scan the Conversation
Walk through the full conversation history and extract:
- What was built or decided - Not what was discussed. What was confirmed, produced, or locked in.
- What's still open - Decisions pending, options still being weighed, things deferred.
- Strategic reasoning - The WHY behind key decisions. Not "we discussed using profit share" but "profit share was chosen because it incentivizes margin discipline, not just volume."
- - Anything the session built on that hasn't been verified. These are landmines for the next session if unlabeled.
