handoff

Create a handoff document summarizing conversation context for another agent.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents lost context when switching agents by compacting an ongoing conversation into a single handoff document the next agent can immediately continue.

Core Features & Use Cases

  • Conversation summarization: Produces a concise handoff that captures the current state, decisions, and remaining work.
  • Artifact de-duplication: Avoids repeating content already captured elsewhere by referencing existing PRDs, plans, ADRs, issues, commits, diffs, or paths/URLs.
  • Next-session guidance: Uses any provided arguments to tailor what the next session should focus on and suggests relevant skills for continuity.

Quick Start

Ask the AI to generate a handoff document for a fresh agent by summarizing the current conversation and saving it to a temporary file using mktemp -t handoff-XXXXXX.md.

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 prior decisions?

To transfer conversation context, you can generate a handoff document that compacts the current session state, decisions, and remaining work into a clean next-agent plan. This preserves task continuity by capturing the context in a single file.

What is the best way to create a handover document for a session restart?

The best way to create a handover document for a session restart is to summarize the ongoing conversation and save it to a temporary file path generated by mktemp. This ensures the next agent receives a clean, reliable continuation plan.

How does context transfer handle existing artifacts like PRDs and commits?

Context transfer handles existing artifacts through artifact de-duplication, which avoids repeating content already captured in PRDs, plans, ADRs, issues, or commits. The handoff document simply references these existing paths or URLs.

Can I tailor what the next session focuses on when switching agents?

Yes, you can tailor what the next session focuses on by providing specific arguments during the handoff document generation. This guides the next agent's priorities and suggests relevant skills for task continuity.

Do I need YAML frontmatter to generate a handoff document?

Yes, generating a handoff document requires YAML frontmatter metadata containing the name and description. This metadata ensures the document is properly structured for the next agent to parse and continue the workflow.