handoff

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a conversation grows long or a session ends, context is lost and the next agent or session must start from scratch. 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 session into a handoff document saved to the OS temporary directory, keeping the workspace clean. - Suggested Skills Section: Recommends which skills the next agent should invoke to continue the work effectively. - Artifact Referencing: Avoids duplicating content already captured in PRDs, plans, ADRs, issues, commits, or diffs by referencing them via path or URL. - Sensitive Data Redaction: Strips API keys, passwords, and personally identifiable information from the handoff. - Use Case: Before ending a long debugging or feature-building session, invoke the handoff skill with a note like "next session: write integration tests" so the next agent receives a tailored, redacted summary. ## 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 hand off an AI agent conversation to a new session?▼

Invoke the handoff skill at the end of your 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's key decisions and state, reference existing artifacts like PRDs, plans, and commits by path or URL, 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 include secrets or API keys?▼

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

When should I not use a conversation handoff summary?▼

Avoid it when all relevant context is already captured in durable artifacts like commits, issues, or ADRs, since the handoff should reference those rather than duplicate them. It adds the most value for uncommitted reasoning and session state.