handoff

Writes a conversation summary document for a fresh agent to continue the work.

Updated Jan 19, 2023
One-click install
npx skills add https://github.com/inkfin/dotfiles --skill handoff-inkfin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/inkfin/dotfiles/tree/main/dot_agents/skills/exact_handoff
Command: npx skills add https://github.com/inkfin/dotfiles --skill handoff-inkfin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a conversation grows long or a session must end, context is lost and the next agent or session starts from zero. This Skill compacts the current conversation into a structured handoff document so a fresh agent can pick up the work without re-reading the entire history. ## Core Features & Use Cases - Conversation Compaction: Summarizes the current conversation into a handoff document saved to the operating system's 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 instead. - Suggested Skills Section: Recommends which skills the next agent should invoke to continue the work effectively. - Sensitive Data Redaction: Removes API keys, passwords, and personally identifiable information from the handoff. - Use Case: Before ending a long debugging session, invoke the handoff with a note like "next session: implement the fix" so the next agent receives a tailored, redacted summary pointing at the relevant plan files. ## Quick Start Ask the agent 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 hand off an AI agent conversation to a new session?

Invoke the handoff skill before ending the session. It writes a summary document to your OS temporary directory that a fresh agent can read to resume the work, and you can pass an argument describing the next session's focus.

What should a handoff document include for agent continuity?

A handoff document should summarize the conversation, reference existing artifacts like specs, plans, and commits by path or URL rather than duplicating them, and include a suggested skills section telling the next agent which skills to invoke.

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 project repository free of transient session files.

Does the handoff document protect sensitive information?

Yes. The skill redacts sensitive information such as API keys, passwords, and personally identifiable information before writing the document, so secrets are not carried into the handoff file.

Can I customize the handoff for what the next session will do?

Yes. Pass arguments describing what the next session will focus on, and the skill treats them as guidance to tailor the handoff document's content and emphasis accordingly.