handoff

Write a compact handoff document summarizing conversation context for another agent.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/kileroppo/AI-Coding-Guidance-Skills --skill handoff-kileroppo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/kileroppo/AI-Coding-Guidance-Skills/tree/main/skills/handoff
Command: npx skills add https://github.com/kileroppo/AI-Coding-Guidance-Skills --skill handoff-kileroppo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Handoff documents prevent context loss by converting an ongoing conversation into a concise, actionable summary that another agent can immediately continue.

Core Features & Use Cases

  • Conversation Compaction: Summarizes the current discussion into a ready-to-use artifact for a fresh agent session.
  • Argument-Aware Next Focus: Tailors the handoff to the user-provided argument that describes what the next session should focus on.
  • Artifact De-Duplication: Avoids repeating information already captured in existing PRDs, plans, ADRs, issues, commits, diffs by referencing their paths or URLs instead.
  • Next-Skill Suggestions: Recommends which skills (if any) should be used by the next session to continue efficiently.

Quick Start

Use the handoff skill to create a continuation document for a new agent by stating what the next session should focus on.

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?

Summarize conversation context for agent reassignment by generating a compact handoff document that preserves decisions, progress, and constraints. This artifact is written to a temporary file path, allowing a fresh agent session to continue immediately without losing prior context.

What's the best way to summarize an ongoing chat session for a fresh agent context?

The best way to summarize a chat session is creating a handoff document that compacts the conversation into an actionable summary. It references existing artifacts like PRDs, ADRs, and commits by path or URL instead of duplicating them, ensuring the new agent gets concise context.

How does a handoff document handle existing project artifacts like PRDs and commits?

A handoff document handles existing project artifacts by referencing their file paths or URLs instead of duplicating their contents. This artifact de-duplication ensures the compact summary remains concise while still pointing the next agent to relevant plans, issues, and diffs.

Can I tailor the context transfer summary for a specific next-session focus?

Yes, you can tailor the context transfer summary by providing an argument that describes what the next session should focus on. The handoff document uses this argument to align the summarized decisions and next-skill suggestions with your specific continuation goals.

Does generating an agent handoff note require writing to a specific file path?

Generating an agent handoff note requires writing the summary to a mktemp-generated file path. This ensures the compact context transfer document is saved as a ready-to-use artifact that the next agent session can immediately access and read.