handoff

Summarize a conversation into a handoff document with redactions and artifact references.

1|Updated Mar 19, 2026

Search Tags:#summarization #handoff #session continuity #agent coordination #redaction #context transfer

Ready to run

npx skills add https://github.com/ian-pascoe/dotfiles-chezmoi --skill handoff-ian-pascoe

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/ian-pascoe/dotfiles-chezmoi/tree/main/dot_agents/skills/handoff
Command: npx skills add https://github.com/ian-pascoe/dotfiles-chezmoi --skill handoff-ian-pascoe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns an in-progress conversation into a concise handoff document so another agent can resume work without losing context.

Core Features & Use Cases

Summarizes the current discussion into a portable briefing for the next session.
Redacts sensitive information such as keys, passwords, and personal data.
Points to existing artifacts instead of duplicating PRDs, plans, issues, or diffs.
Suggests follow-up skills and adapts the handoff to the next session's goal.
Use it when a task needs to be paused, transferred, or continued by a different agent.

Quick Start

Create a handoff document for this conversation, tailor it to the next session's focus, and save it in the user'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 agent context to another session without losing key decisions?▼

Creating a handoff document transfers agent context by summarizing the current conversation, preserving key decisions, and referencing existing artifacts without duplicating them, ensuring the next session starts with complete continuity.

What is the best way to summarize a conversation for a different agent to continue work?▼

The best way to summarize a conversation for another agent is to create a portable handoff briefing that captures the discussion's current state, points to existing PRDs or diffs, and suggests follow-up skills for the next turn.

Does handoff documentation redact sensitive information like passwords and keys?▼

Yes, handoff documentation redacts sensitive information like keys, passwords, and personal data during the summarization process, ensuring the context transfer remains secure before being saved outside the workspace.

Can I save a session continuity document outside my current workspace?▼

Yes, you can save a session continuity document outside your current workspace. The handoff process exports the portable briefing into the user's temporary directory for follow-up tasks.

When should I use a context transfer document instead of copying project artifacts directly?▼

You should use a context transfer document when a task needs to be paused or transferred. It references existing artifacts like PRDs, plans, issues, and diffs instead of duplicating them, preventing redundancy while maintaining context.

What limitations exist when adapting a handoff document to a next session's goal?▼

A key limitation is that adapting a handoff document requires you to explicitly state the next session's focus. The document only suggests follow-up skills and summarizes past context; it does not execute the next task automatically.