handoff

Create a handoff document summarizing conversation context, open questions, and next steps.

12|4|Updated May 14, 2012
One-click install
npx skills add https://github.com/sethvoltz/dotfiles --skill handoff-sethvoltz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/sethvoltz/dotfiles/tree/main/claude/claude/skills/handoff
Command: npx skills add https://github.com/sethvoltz/dotfiles --skill handoff-sethvoltz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns an active conversation into a concise handoff document so another agent can continue the work without losing context, duplicating effort, or missing important references.

Core Features & Use Cases

  • Conversation Compression: Summarizes the current thread into a structured briefing for the next session.
  • Context Preservation: Captures goals, decisions, open questions, and next steps while avoiding repetition of material already stored elsewhere.
  • Safe Transfer: Redacts sensitive information and points to existing artifacts by path or URL instead of copying them.
  • Use Case: Useful when a task needs to pause and resume later, or when work must be handed off to a fresh agent with the right focus.

Quick Start

Ask the skill to create a handoff document for the current conversation focused on the next session’s goal and save it to your operating system’s temporary directory.

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 another agent without losing details?

To transfer conversation context to another agent, generate a structured handoff document that captures goals, decisions, open questions, and next steps. This concisely preserves the working context without duplicating material already stored elsewhere, ensuring a seamless agent transition.

What is the best way to create an agent workflow handoff summary for paused tasks?

The best way to create an agent workflow handoff summary for paused tasks is to compress the active conversation into a concise briefing. This captures goals, decisions, open questions, and next-step guidance while avoiding repetition of material already stored in existing artifacts.

Does context transfer between agents require sensitive data redaction?

Yes, context transfer between agents requires sensitive data redaction to ensure safe transfer. The handoff process points to existing artifacts by path or URL instead of copying them, which further protects sensitive information during multi-session collaboration and agent transitions.

How do I redact sensitive information when summarizing a conversation for another agent?

To redact sensitive information when summarizing a conversation for another agent, the handoff document applies safe transfer rules. It redacts sensitive data and references existing artifacts by path or URL instead of duplicating the content directly in the summary.

Can I save a handoff document to my operating system's temporary directory?

Yes, you can save a handoff document to your operating system's temporary directory. You simply ask the skill to create a handoff document for the current conversation focused on the next session's goal and specify the temporary directory as the save destination.

What limitations exist when using conversation compression for multi-session collaboration?

A key limitation of conversation compression for multi-session collaboration is that it avoids duplicating material already stored elsewhere by referencing existing artifacts by path or URL. It focuses on concise context, open questions, and next-step guidance rather than recreating full conversation histories.