handoff

Writes a conversation summary handoff document for a fresh agent session.

Updated Feb 22, 2024
One-click install
npx skills add https://github.com/tlipoca9/dotfiles --skill handoff-tlipoca9
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/tlipoca9/dotfiles/tree/main/home/dot_agents/skills/handoff
Command: npx skills add https://github.com/tlipoca9/dotfiles --skill handoff-tlipoca9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a conversation grows long or a task must continue in a new session, context is lost. This Skill compacts the current conversation into a 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 OS temporary directory, keeping the workspace clean. - Suggested Skills Section: Names which skills the next agent should invoke, so the follow-up session starts with the right capabilities. - Artifact Referencing and Redaction: References existing specs, plans, ADRs, issues, commits, and diffs by path or URL instead of duplicating them, and redacts sensitive data such as API keys, passwords, and personally identifiable information. - Use Case: After a long debugging session, ask for a handoff focused on "finishing the database migration"; the next agent receives a tailored summary pointing at the relevant plan and diff files. ## Quick Start Ask the agent to create a handoff document for the next session, optionally describing what that 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 continue an AI agent task in a new session?▼

Create a handoff document that summarizes the current conversation and save it to the OS temporary directory. The next agent reads that document to resume the work without replaying the full history.

What should a handoff document include for the next agent?▼

A handoff document should summarize the conversation, include a suggested skills section naming which skills the next agent should invoke, and reference existing artifacts like specs, plans, ADRs, issues, commits, and diffs by path or URL.

Where is the handoff document saved?▼

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

Does the handoff document protect sensitive information?▼

Yes, the handoff process redacts sensitive information such as API keys, passwords, and personally identifiable information before writing the document. It also avoids duplicating content already captured in other artifacts.

Can I tailor the handoff for a specific next task?▼

Yes, pass an argument describing what the next session will focus on, and the handoff document is tailored accordingly. This helps the receiving agent prioritize the most relevant context.