handoff

Creates checkpoint documents that let another session or agent resume work without the conversation.

2|Updated Sep 14, 2026
One-click install
npx skills add https://github.com/kwanpham2195/agent-stuff --skill handoff-kwanpham2195
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/kwanpham2195/agent-stuff/tree/main/skills/handoff
Command: npx skills add https://github.com/kwanpham2195/agent-stuff --skill handoff-kwanpham2195

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When a conversation ends or moves to another agent, context is lost. This Skill captures decisions, evidence, progress, and next actions in a durable checkpoint so the next session can resume research, planning, or implementation without repeating work. ## Core Features & Use Cases - Checkpoint Creation: Writes a structured handoff document containing decisions, evidence, unresolved questions, progress, and the next concrete action. - Artifact-Aware Updates: Updates an existing authoritative entry artifact instead of duplicating context, linking other sources rather than copying them. - Environment-Aware Packaging: Lists exact skill paths to load, flags resources unavailable in the target environment, and excludes credentials or sensitive data. - Use Case: You are mid-way through debugging an authentication issue and need to continue tomorrow or on another machine. Use this Skill to write a handoff file capturing findings, pending decisions, and the next step so the next session picks up exactly where you stopped. ## Quick Start Use the handoff skill to write a checkpoint document summarizing our current progress and next steps for the next session.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I hand off work to another AI agent session?▼

Use the handoff skill to write a checkpoint document containing decisions, evidence, unresolved questions, progress, and the next concrete action. The next session reads this file and reconciles current state before continuing work.

What should a handoff document include for continuity?▼

A handoff should include the current objective, decisions made, observed execution and verification results, unresolved questions, the next action, and exact skill paths to load. It should link authoritative sources instead of duplicating their contents.

Where are handoff checkpoint files stored?▼

For continuing project work, the checkpoint goes in the lifecycle's durable location. For one-off transfers with no project home, a unique file is created in the OS temporary directory, with a note that temporary storage may be cleaned up.

Can a handoff document contain credentials or secrets?▼

No. Handoffs explicitly exclude credentials and unnecessary personal information, and a handoff cannot be used to authorize additional actions. Pending decisions and withheld permissions are preserved as-is.

When should I update an existing artifact instead of creating a new handoff?▼

When an authoritative entry artifact already exists, update it in place rather than creating a second summary. A short entry note linking authoritative sources is enough when a plan or research artifact already carries the context.