handoff

Summarize the current conversation into a structured handoff document referencing artifacts by path or URL.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Compact the current conversation into a handoff document for another agent to pick up, referencing existing artifacts by path or URL instead of duplicating content. This enables continuity and reduces rework when switching agents or sessions.

Core Features & Use Cases

  • Artifact-aware summarization: creates a concise handoff that cites PRDs, plans, ADRs, issues, commits, and diffs by their paths or URLs.
  • Non-duplication: avoids reprinting content already captured in other artifacts.
  • Structured template: includes sections like Goal of next session, State of play, Open decisions, Skills to use, Artifacts.
  • Next-session guidance: suggests relevant skills for the next agent/session based on the current context.

Quick Start

Create a new handoff document for the current conversation by running mktemp -t handoff-XXXXXX.md and reference artifacts by path or URL.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I create a conversation handoff document for another agent?

A conversation handoff document compacts your current session context into a structured template, referencing existing artifacts by path or URL instead of duplicating content to ensure continuity for the next agent.

What is artifact-aware summarization for agent session continuity?

Artifact-aware summarization compacts active context into a handoff document that cites PRDs, plans, ADRs, issues, commits, and diffs by path or URL, avoiding content duplication and preserving prior work.

How do I reference existing PRDs and issues without duplicating content in handoffs?

You reference existing PRDs and issues without duplicating content by citing their file paths or URLs in the handoff document, structurally avoiding reprinting content already captured in other artifacts.

Can I suggest relevant skills for the next agent session in a handoff document?

Yes, the structured handoff template includes a Skills to use section that suggests relevant skills for the next agent session based on the current context to guide continuity.

What sections should a structured handoff document include?

A structured handoff document should include Goal of next session, State of play, Open decisions, Skills to use, and Artifacts sections to ensure continuity and reduce rework when switching agents.

When do I need to generate a handoff document for switching agents?

You need to generate a handoff document when switching agents or sessions that require continuity of work, preserving prior context and reducing rework by referencing existing artifacts by path or URL.