handoff

Writes a session handoff document that a fresh conversation can resume work from.

2|Updated Jul 24, 2026
One-click install
npx skills add https://github.com/konstantinos-malavazos/claude-code-playbook --skill handoff-konstantinos-malavazos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/konstantinos-malavazos/claude-code-playbook/tree/main/templates/skills/handoff
Command: npx skills add https://github.com/konstantinos-malavazos/claude-code-playbook --skill handoff-konstantinos-malavazos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a working session ends or hits a context limit, decisions, open questions, and unwritten constraints vanish with the conversation. This Skill compacts the current session into a single handoff file so a fresh session can resume the work without re-deriving what was already settled. ## Core Features & Use Cases - Root-level file placement: Writes one file per subject to the root of <workspace>/.claude/handoffs/, matching the SessionEnd hook that deletes subdirectories but preserves root-level files. - Supersede, don't duplicate: Reads any existing handoff for the same subject before overwriting, carrying forward open questions and decisions from prior sessions. - Unrecoverable-first structure: Leads with what a fresh session cannot reconstruct (uploaded files, verbal constraints, rejected approaches) and references rather than duplicates memory, tickets, and commits. - Use Case: You are approaching the context limit mid-ticket. Invoke the handoff skill with the next session's focus, and it writes handoff-<TICKET-ID>.md containing the resume point, decisions with reasoning, and suggested skills for the next session. ## Quick Start Ask the assistant to write a handoff for the current session focused on what the next session should work 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 work between Claude Code sessions?

Invoke the handoff skill at the end of a session or before hitting the context limit. It writes a single Markdown file to .claude/handoffs/ containing the resume point, decisions with reasoning, and open questions, which a fresh session reads to continue.

Where should session handoff files be saved?

Handoff files must be saved at the root of .claude/handoffs/, never inside a subdirectory. The SessionEnd cleanup hook deletes every subdirectory of the handoffs root while preserving root-level files, so a nested handoff is silently removed.

What should a session handoff document include?

Lead with what a fresh session cannot recover, such as uploaded files or verbal constraints. Then record the resume point, decisions with their reasoning, open questions for the user, and suggested skills, while referencing rather than duplicating memory, tickets, and commits.

Can I have multiple handoff files for the same ticket?

Only one live handoff per subject is allowed; a new handoff reads and supersedes the old one. The exception is a genuinely different focus for the next session, which gets a suffixed second file with cross-references between the two.

When should I not write a handoff document?

Skip the handoff when the work is finished and merged with nothing open. In that case a single line stating completion is enough, since a handoff nobody will read adds noise without value.