handoff

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

Updated Sep 5, 2023
One-click install
npx skills add https://github.com/eyenalxai/dotfiles --skill handoff-eyenalxai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/eyenalxai/dotfiles/tree/main/.agents/skills/handoff
Command: npx skills add https://github.com/eyenalxai/dotfiles --skill handoff-eyenalxai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a conversation grows long or a task needs to move to a fresh agent session, context is lost. This Skill compacts the current conversation into a structured handoff document so another agent can pick up the work without repeating prior discussion. ## Core Features & Use Cases - Conversation Compaction: Summarizes the current conversation into a handoff document saved to the OS temporary directory, keeping the workspace clean. - 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 document. - Use Case: After a long debugging session, invoke the handoff skill with a note like "next session will implement the fix" to produce a tailored summary document a fresh agent can use to continue immediately. ## Quick Start Ask the agent to create a handoff document summarizing this conversation so a new session can continue the work.

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 generate a summary document of the current conversation. The document is saved to your OS temporary directory, and you can pass an argument describing what the next session will focus on to tailor the content.

Where is the handoff document saved?

The handoff document is saved to the temporary directory of your operating system, not the current workspace. This keeps your project repository free of transient session files.

Does the handoff document include sensitive information like API keys?

No. The skill explicitly redacts sensitive information such as API keys, passwords, and personally identifiable information before writing the handoff document.

Will the handoff duplicate my specs, plans, or commit history?

No. Content already captured in artifacts like specs, plans, ADRs, issues, commits, or diffs is referenced by path or URL rather than duplicated, keeping the handoff document concise.

When should I not use a handoff document?

Avoid it when all relevant context already exists in durable artifacts like issues or ADRs, since the handoff only references those. It adds the most value when conversational decisions and reasoning are not yet recorded anywhere.