handoff

Name: handoff
Availability: InStock
Author: Spontus

Summarize an ongoing conversation into a compact handoff document.

1|Updated May 22, 2026

Search Tags:#summarization #handoff #session continuity #agent collaboration #workflow planning #context transfer

Ready to run

npx skills add https://github.com/spontus-reach/spontus --skill handoff-spontus-reach

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/spontus-reach/spontus/tree/main/.agents/skills/handoff
Command: npx skills add https://github.com/spontus-reach/spontus --skill handoff-spontus-reach

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents losing context by converting the current conversation into a compact handoff document that another agent can immediately continue.

Core Features & Use Cases

Conversation summarization for continuity: Produces a concise document capturing what matters most for the next agent.
Next-session focus alignment: Tailors the handoff based on the provided argument describing what the next session will be used for.
Artifact de-duplication: Avoids repeating content already captured elsewhere by referencing existing artifacts by path or URL instead.

Quick Start

Ask the agent to create a handoff document that summarizes this conversation and saves it to a mktemp-generated file path.

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 progress?▼

To transfer conversation context, this Skill summarizes the ongoing chat into a compact handoff document, ensuring another agent can resume multi-stage task execution without context loss.

What is the best way to summarize a chat session for a restart?▼

The best way to summarize a chat session for a restart is to generate a concise handoff document that captures operational context and references existing artifacts by path or URL to avoid duplication.

Do I need to specify a file path when creating a conversation handoff?▼

Yes, the handoff process requires writing the summarized document to a temporary mktemp-generated file path, ensuring the context transfer output is safely stored for the next agent session.

Can I align the conversation summarization focus for the next session?▼

Yes, you can align the conversation summarization focus by providing an argument describing what the next session will be used for, tailoring the handoff document to specific workflow planning requirements.

How does artifact de-duplication work during session continuity handoffs?▼

Artifact de-duplication during session continuity works by referencing existing artifacts by path or URL instead of repeating their content, keeping the handoff document compact and avoiding duplication.

When should I avoid using a compact handoff document for agent collaboration?▼

You should avoid using a compact handoff document when a conversation lacks sufficient operational context or existing artifacts to reference, as the summary would not provide meaningful continuity for multi-stage task execution.