handoff

Compress a conversation into a temporary markdown handoff document.

2|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/miptah21/skills --skill handoff-miptah21
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/miptah21/skills/tree/main/.agents/skills/handoff
Command: npx skills add https://github.com/miptah21/skills --skill handoff-miptah21

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the need to manually re-explain ongoing work by converting a conversation into a concise handoff document another agent can immediately continue.

Core Features & Use Cases

  • Conversation Compression into a Handoff: Summarizes the current state of progress so continuity is preserved across sessions.
  • Artifact-Aware Referencing: Avoids duplicating content already captured elsewhere (PRDs, plans, ADRs, issues, commits, diffs) by referencing them by path or URL.
  • Argument-Guided Next-Step Focus: When a user provides arguments, the handoff is tailored to what the next session should accomplish.

Use Case: After a planning or implementation session, generate a handoff so a new agent can pick up remaining tasks, constraints, and decisions without rereading the entire chat.

Quick Start

Use the handoff skill to produce a handoff document that a fresh agent can use to continue the current work.

Frequently Asked Questions about handoff

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I summarize a conversation for another agent to continue?

To summarize a conversation for another agent, generate a handoff document that compacts ongoing work into a concise markdown file. This enables seamless session continuity by capturing key decisions and status without requiring the next agent to reread the entire chat.

What is the best way to preserve task continuity across multiple agent sessions?

Task continuity across multiple agent sessions is preserved by creating a conversation summary that extracts key decisions and current progress. The handoff document references existing artifacts like PRDs and commits by path or URL to avoid content duplication.

Can I tailor the handoff summary to focus on specific next steps?

Yes, you can tailor the handoff summary by providing arguments that guide the focus. When arguments are provided, the generated handoff document is customized to highlight what the next session should specifically accomplish, ensuring targeted task continuation.

How does the handoff document handle existing project artifacts?

The handoff document handles existing project artifacts by referencing them by path or URL rather than duplicating their content. It ensures artifact-aware referencing for documents like PRDs, plans, ADRs, issues, commits, and diffs to keep the summary concise.

Where is the generated handoff markdown file saved?

The generated handoff markdown file is saved to a fresh temporary file created via mktemp. This produces a clean document that a fresh agent can immediately use to continue the current work without modifying existing project files.

When do I need to create a handoff document for agent coordination?

You need to create a handoff document for agent coordination after a planning or implementation session ends. It is required for multi-session agent workflows where a new agent must pick up remaining tasks, constraints, and decisions without rereading the chat.