handoff

Name: handoff
Availability: InStock
Author: enduser123

Capture session state and generate structured handover documents for Claude Code.

Updated Apr 23, 2026

Search Tags:#automation #documentation #handoff #ADR #precompact #session-continuity #quality-scoring

Ready to run

npx skills add https://github.com/EndUser123/cc-skills-utils --skill handoff-enduser123

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/EndUser123/cc-skills-utils/tree/main/skills/handoff
Command: npx skills add https://github.com/EndUser123/cc-skills-utils --skill handoff-enduser123

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a robust framework to automatically capture and preserve work context across sessions, handoffs, and compacts, ensuring continuity when transitioning between Claude Code sessions or agents.

Core Features & Use Cases

Automatic capture via PreCompact hooks for seamless handover documents
Manual operations via python -m scripts.cli for debugging and restoration
Structured handover storage with JSON-based documents and retention policies
Context-driven continuation via ADRs, objectives, and knowledge contributions

Quick Start

Install the handoff package and rely on automatic capture before compact; use the CLI only if you need debugging or manual restoration.

Frequently Asked Questions about handoff

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

FAQPage Schema

How do I maintain session continuity when transitioning between Claude Code agents?▼

Session continuity is maintained by automatically capturing state and generating durable handover artifacts, ensuring uninterrupted work when transitioning between Claude Code agents or compacts. Structured JSON documents preserve context.

How does automatic context capture work during a precompact hook?▼

Automatic context capture works via PreCompact hooks that seamlessly generate handover documents. It captures objectives, ADRs, and knowledge contributions before compacts, ensuring structured handover storage with quality scoring and retention policies.

What is the best way to document session handoffs for cross-session continuity?▼

Documenting session handoffs is best handled through structured JSON-based documents that automatically capture session state. This ensures durable handover storage with context-driven continuation via ADRs and retention policies.

Can I manually restore session state if the automatic handover fails?▼

Manual restoration is supported through python -m scripts.cli, allowing you to debug and manually restore session state. This provides a fallback for ensuring cross-session continuity when automatic capture is insufficient.

Do I need to configure retention policies for session handover documents?▼

Retention policies are configurable for session handover documents, allowing you to manage structured handover storage. You can define retention rules alongside configurable paths to control how long context artifacts persist.

When should I avoid automatic context capture for agent transitions?▼

Automatic context capture may be unnecessary for trivial agent transitions or single-session tasks. If debugging or manual restoration is needed, bypass automatic hooks and use the CLI tooling for controlled session handovers.