session-handoff

Generates a reason-first re-entry prompt for forking tangent sessions with clean context.

3|Updated Oct 28, 2020
One-click install
npx skills add https://github.com/k0d3x8its/dotfiles --skill session-handoff-k0d3x8its
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-handoff
Source: https://github.com/k0d3x8its/dotfiles/tree/main/claude/.claude/skills/session-handoff
Command: npx skills add https://github.com/k0d3x8its/dotfiles --skill session-handoff-k0d3x8its

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a side-issue appears mid-session, chasing it pollutes the main conversation's context. This Skill forks a focused tangent by emitting a compact re-entry prompt (reason, scope, first action) so you can open a fresh session to handle the side-issue without losing the main thread. ## Core Features & Use Cases - Tangent Forking: Builds a reason-first re-entry prompt with bounded scope, a concrete first action, and 1-3 suggested skills for the tangent. - Light TODOS Sync: Notes or appends related open items in TODOS.md, supporting both flat and .work/plan planning formats, without writing SESSION-LOG narrative. - Crash-Safe Output: Saves the re-entry prompt to /tmp/handoff-{timestamp}.md so it survives terminal crashes. - Use Case: While debugging a feature, you notice an unrelated test gap. Run /handoff to spin off a clean session for the test work, then use /handoff-return to merge findings back into the still-open main session. ## Quick Start Run /handoff with an optional focus description to generate a tangent re-entry prompt you can paste into a new session.

Frequently Asked Questions about session-handoff

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fork a tangent session in Claude Code without losing context?▼

Run /handoff with an optional focus argument. It prints a re-entry prompt containing the reason, scope, and first action, which you paste into a new session. The main session stays open for /handoff-return later.

What is the difference between /handoff and /checkpoint?▼

/handoff is a lightweight mid-session fork that passes context between adjacent sessions and writes no SESSION-LOG narrative. /checkpoint is the durable end-of-day wrap-up that records full narrative for long-term memory.

Does the handoff prompt survive a terminal crash?▼

Yes. The re-entry prompt is saved to /tmp/handoff-{timestamp}.md, so it survives a terminal crash or accidental tab exit. The file is not project-specific and is cleaned up by the OS on reboot.

How do I merge tangent findings back into the main session?▼

When the tangent session finishes, run /handoff-return. It summarizes the tangent's findings and syncs them to TODOS.md, popping the forked work back into the still-alive main session.

When should I not use /handoff for session management?▼

Avoid /handoff for end-of-day wrap-ups or durable memory needs; use /checkpoint instead. It is designed only for lightweight push/pop context-passing between adjacent sessions, not long-term narrative storage.