handoff

Writes a conversation summary document for a fresh agent to continue the work.

Updated Jun 28, 2026
One-click install
npx skills add https://github.com/AO-HyS/aohys.com --skill handoff-ao-hys
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/AO-HyS/aohys.com/tree/main/.agents/skills/handoff
Command: npx skills add https://github.com/AO-HyS/aohys.com --skill handoff-ao-hys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a conversation grows long or a session must end, context is lost and the next agent or session starts from zero. This Skill compacts the current conversation into a structured handoff document so work can resume without re-explaining prior decisions. ## Core Features & Use Cases - Conversation Compaction: Summarizes the current conversation into a handoff document saved to the operating system's temporary directory, keeping the workspace clean. - Suggested Skills Section: Names which skills the next agent should invoke, so the follow-up session activates the right capabilities immediately. - Artifact Referencing and Redaction: References existing specs, plans, ADRs, issues, commits, and diffs by path or URL instead of duplicating them, and redacts sensitive data such as API keys, passwords, and personally identifiable information. - Use Case: Before ending a long debugging or implementation session, ask for a handoff describing what the next session will focus on; the resulting document lets a fresh agent pick up exactly where you left off. ## Quick Start Ask the agent to create a handoff document for the next session, optionally describing what that session will focus on.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I hand off a conversation to another AI agent?▼

Invoke the handoff skill and optionally describe what the next session will focus on. It writes a summary document to your OS temporary directory that a fresh agent can read to resume the work.

What should a handoff document include for the next session?▼

A handoff document should summarize the conversation, reference existing artifacts like specs, plans, ADRs, issues, commits, and diffs by path or URL, and include a suggested skills section naming which skills the next agent should call.

Where is the handoff document saved?▼

The handoff document is saved to the temporary directory of the user's operating system, not the current workspace. This keeps the project repository free of transient session files.

Does the handoff document include API keys or personal data?▼

No. The skill explicitly redacts sensitive information such as API keys, passwords, and personally identifiable information before writing the document, so secrets are not carried into the next session.

When should I use a handoff instead of continuing the same session?▼

Use a handoff when the conversation is approaching context limits, when switching agents or models, or when a different session will handle the next phase of work. It avoids duplicating content already captured in specs, plans, or commits.