handoff

Capture and transfer project state into a root-level HANDOFF.md file.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/ToanPV90/dotfiles --skill handoff-toanpv90
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/ToanPV90/dotfiles/tree/main/claude/.claude/skills/handoff
Command: npx skills add https://github.com/ToanPV90/dotfiles --skill handoff-toanpv90

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents stalled progress when a conversation gets too long or needs to pause by capturing the current state so another agent can immediately continue from the right footing.

Core Features & Use Cases

  • Project handoff creation: Creates or updates a standardized project-root HANDOFF.md with clear sections for goal, progress, outcomes, and next steps.
  • Session history linking: Searches recent session summaries for the current project and includes the last three relevant entries to preserve continuity.
  • Dual persistence update: Saves both the HANDOFF.md document and a session summary via context-manager save so downstream agents can retrieve the same state.

Quick Start

Ask the agent to perform a handoff for this project by creating or updating HANDOFF.md in the project root and saving a corresponding session summary.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I transfer project status to a new agent when context is full?

To transfer project status to a new agent when context is full, you need a handoff document. This Skill captures the current state by writing a root-level HANDOFF.md with goal, progress, and next steps, and saves a session summary to preserve continuity.

What is the best way to preserve session history for agent collaboration?

The best way to preserve session history for agent collaboration is linking recent summaries. This Skill searches the local sessions index and enriches the handoff document with the last three relevant entries to ensure downstream agents retrieve the same state.

How do I create a handoff document for continuing project work?

You create a handoff document by asking the agent to perform a handoff. It generates or updates a standardized HANDOFF.md in the project root containing required sections for outcomes and next steps, then persists the summary through context-manager save.

When do I need to generate a project handoff file?

You need to generate a project handoff file when a conversation gets too long, needs to pause, or when an assistant must start fresh in a new session. It prevents stalled progress by capturing the current state for the next agent.

Does this handoff approach work without external dependencies?

Yes, this handoff approach works without external dependencies. It operates standalone to create the HANDOFF.md and integrate with the local sessions index and context-manager to save the state, requiring no additional setup.

Why does my agent lose context when starting a new session?

Your agent loses context when starting a new session because previous state is not automatically transferred. Writing a standardized handoff document with recent session history prevents this by giving the new agent the required project footing.