handoff

Summarize a conversation into a handoff markdown file for the next agent.

1|1|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/ntk148v/skills --skill handoff-ntk148v
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/ntk148v/skills/tree/main/skills/handoff
Command: npx skills add https://github.com/ntk148v/skills --skill handoff-ntk148v

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents losing critical context by compacting a conversation into a handoff document another agent can continue immediately.

Core Features & Use Cases

  • Conversation Compaction: Summarizes the current discussion into a concise continuation-ready artifact.
  • Deduplication by Artifacts: Avoids repeating content already captured elsewhere (PRDs, plans, ADRs, issues, commits, diffs) by referencing their locations.
  • Next-Session Targeting: Tailors the handoff based on any provided arguments describing the next session’s focus.

Quick Start

Use the handoff skill to write a continuation document to a temporary path produced by mktemp so a fresh agent can resume the work.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I preserve project context when handing off to a new agent?

Preserve project context during an agent handoff by summarizing the conversation into a continuation-ready markdown document, allowing a new agent to resume seamlessly without losing critical context or duplicating existing artifacts.

How does conversation summarization work for multi-agent task handoffs?

Conversation summarization for multi-agent task handoffs compacts the current discussion into a concise transfer document, referencing existing artifacts by path or URL to avoid repeating content already captured in PRDs, plans, or commits.

Can I target the next session focus when creating a handoff document?

Yes, you can tailor the handoff document by providing arguments that describe the next session's focus, ensuring the new agent receives context specifically targeted for its upcoming tasks.

Do I need a temporary file path to write an agent handoff document?

Yes, you need to use mktemp to create a temporary file path for writing the handoff markdown, allowing a fresh agent to immediately locate and resume the work.

How do I avoid duplicating existing artifacts like PRDs and ADRs in a handoff?

Avoid duplicating existing artifacts like PRDs and ADRs by referencing their locations by path or URL within the handoff document, keeping the transfer file concise while preserving context.