handofflisted

Write a structured session-handoff doc so a fresh Claude session can resume the current work cold — same decisions, same task state, same world state, same do-not-re-litigate guardrails. The canonical response when conversational context gets full and quality starts degrading. Use proactively when the user says or clearly implies any of: explicit slash commands (/handoff, /handoff-resume, /handoff-list, /handoff-done, /handoff-revive, /handoff lean, /handoff emergency); context-pressure framings ("getting close to context limits", "this convo is getting long", "save the session state", "dump what I've got so a fresh session can pick up", "context rescue", "session transfer"); mid-mode framings ("im in the middle of orchestrating", "about to checkpoint this phase mid-flight", "this brainstorm is getting deep, wanna save it", "i need to bail out of this session"); or resume-side language ("yesterday i left off mid-something, can you pick up", "what was i working on", "there's a pending handoff somewhere", "pick
unifylabs-dev/unify-kit · ★ 0 · Code & Development · score 63

Install: claude install-skill unifylabs-dev/unify-kit

# Handoff — universal session-to-session knowledge transfer This skill makes session→session knowledge transfer a first-class primitive. When context pressure threatens a session's deliverable quality, the user (or Claude with discretion) invokes `/handoff` to write a structured document that a fresh Claude session can pick up cold — same decisions, same task state, same world state, same do-not-re-litigate guardrails. The skill ships alongside a `context-awareness.sh` hook (registered on `UserPromptSubmit` + `SessionStart`) and an additive extension to the `phasing` skill (a `phase-N-checkpoint.md` flow + `/phase-continue` for the phase-executor mid-flight case). Together they cover the four transition types from the design spec. --- ## Why this skill exists The founder regularly notices conversational context approaching pressure thresholds (35% awareness, 45–50% reset target) across multiple workflow modes — phasing orchestrator, phasing executor, brainstorming, plan execution, free conversation. Without a canonical handoff machinery, the response is manual and inconsistent: the founder asks Claude to "write a handoff doc", which is often too late, has no consistent shape, and loses crucial conversational nuance (mid-conversation locks, direction changes, surveyed-and-rejected options). The gap matrix the design spec identified: | Scenario | Has handoff today? | Triggered by? | Documented in skill? | |---|---|---|---| | Phase end → next phase (`phase-N-handoff.md`)