kc-session-handoff

Write journal entries with resume prompts containing parsed handoff IDs from git sessions.

3|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/iamcxa/kc-claude-plugins --skill kc-session-handoff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kc-session-handoff
Source: https://github.com/iamcxa/kc-claude-plugins/tree/main/kc-hyperfocus/skills/kc-session-handoff
Command: npx skills add https://github.com/iamcxa/kc-claude-plugins --skill kc-session-handoff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture and preserve the essential state of a development session when context pressure is high or a handoff is required, so the next session can resume quickly without manual reconstruction of branch, working directory, or recent work.

Core Features & Use Cases

  • Structured handoff journaling: Writes a project-scoped journal entry with a required "Session Handoff:" header and a one-line description.
  • Reliable resume ID: Calls the MCP process_thoughts tool, parses the returned handoff_id, verifies repo-scoped writes, and retries on failure to ensure a usable resume identifier.
  • Context restoration hygiene: Records branch, working directory, linked worktree info, optional technical insights to MEMORY.md, optional context-lake caching of file insights, and emits handoff metrics.
  • Use Case: Ideal for pausing work in a complex multi-directory repo or linked worktree before meetings, code reviews, or end-of-day sessions so teammates or future sessions can restart exactly where you left off.

Quick Start

Run /kc-session-handoff with an optional focus note to record the session, capture a handoff ID, and return a one-line resume prompt for the next session.

Frequently Asked Questions about kc-session-handoff

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

FAQPage Schema
How do I preserve git worktree state for session handoff?

Session handoff journaling works by writing a project-scoped entry with a required 'Session Handoff:' header, calling the process_thoughts tool to parse a reliable handoff_id, and verifying the write with retries to ensure a usable resume identifier.

Can I resume a debugging session after hitting context limits?

You should use session handoff journaling when context pressure is high in multi-directory workspaces or linked worktrees, ensuring that branch, working directory, and recent changes are preserved before meetings, code reviews, or end-of-day pauses.

Does session handoff work with multiple linked worktrees?

The session handoff process optionally appends one-line technical insights to MEMORY.md and stores file insights in the context lake, capturing essential development session state and emitting handoff metrics for later analysis.

What is the best way to generate a resume prompt for a paused coding session?

If the handoff ID write fails, the Skill automatically retries the write operation to ensure a usable resume identifier is generated, preventing context loss during session handoff in complex multi-directory repositories.