handoff

Generates a conversation summary document for continuing work in a new session.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a conversation grows long or a task must continue in a fresh session, context is lost. This Skill compacts the current conversation into a handoff document so a new agent can pick up the work without repeating prior discussion. ## Core Features & Use Cases - Conversation Compaction: Summarizes the current conversation into a structured handoff document saved to the OS temporary directory. - Artifact Referencing: Avoids duplicating content already captured in specs, plans, ADRs, issues, commits, or diffs by referencing them via path or URL. - Sensitive Data Redaction: Removes API keys, passwords, and personally identifiable information from the handoff. - Use Case: After a long debugging session, invoke the handoff skill with a note like "next session will implement the fix" so the next agent receives a tailored summary plus a list of suggested skills to invoke. ## Quick Start Ask the assistant to create a handoff document for the next session, optionally describing what the next session will focus on.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I transfer conversation context to a new agent session?

Invoke the handoff skill to summarize the current conversation into a document saved in your OS temporary directory. The next agent reads this document to resume the work without repeating prior discussion.

How do I tailor a handoff document for the next session?

Pass an argument describing what the next session will focus on, such as the planned task or goal. The skill treats this as guidance and tailors the handoff content accordingly.

Where is the handoff document saved?

The document is saved to the temporary directory of the user's operating system, not the current workspace. This keeps the workspace clean while making the summary accessible to the next session.

Does the handoff document include sensitive information?

No. The skill redacts sensitive data such as API keys, passwords, and personally identifiable information before writing the document, reducing the risk of leaking credentials between sessions.

What are the limitations of a conversation handoff document?

The handoff summarizes rather than fully reproduces context, so fine details may be lost. Content already captured in specs, plans, ADRs, issues, commits, or diffs is referenced by path or URL instead of being duplicated.