handoff

Compact an in-progress agent conversation into a resume-ready handoff document.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/leodiegues/skills --skill handoff-leodiegues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/leodiegues/skills/tree/main/skills/handoff
Command: npx skills add https://github.com/leodiegues/skills --skill handoff-leodiegues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of losing context between agent sessions by converting the current conversation into a clear handoff document that another agent can immediately continue.

Core Features & Use Cases

  • Conversation-to-handoff summarization: Produces a compact document that captures what matters for the next session.
  • Session-focused slug generation: Saves the handoff using a kebab-case slug derived from the session’s actual focus, without overwriting existing files.
  • Artifact de-duplication via references: Avoids repeating content already captured in PRDs, plans, ADRs, issues, commits, or diffs by referencing them by path or URL.

Quick Start

Ask the agent to create a handoff for the next session focused on “auth redirect debugging,” and it will write the document under ~/.claude/handoffs/ with an appropriate slug.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I transfer context between coding agent sessions?

Session continuity is maintained by compacting the current agent conversation into a resume-ready handoff document, ensuring a fresh session can pick up iterative debugging and workflow documentation without losing prior context.

How do I summarize an agent conversation for a fresh session?

Summarizing an agent conversation involves producing a compact handoff document that captures what matters for the next session, generating a kebab-case slug file under ~/.claude/handoffs/ without overwriting existing files.

Can I reference existing artifacts instead of duplicating them in a handoff?

Yes, you can reference existing artifacts by path or URL. The handoff document avoids repeating content already captured in PRDs, plans, ADRs, issues, commits, or diffs, preventing duplication across session transfers.

Does the handoff workflow work for iterative debugging across multiple sessions?

The handoff workflow applies directly to iterative debugging across multiple sessions, converting partial progress and debugging context into a structured document that a fresh coding agent can resume immediately.

What is the best way to document partial progress before switching agents?

The best way to document partial progress is to generate a session-focused handoff that incorporates user-provided next-session arguments and references existing artifacts, writing a kebab-case slug file to preserve workflow continuity.