handoff

Writes a session state note to a git-scoped path for resuming work after a context clear.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? When a Claude Code session is about to be cleared mid-task, everything the session learned risks being lost. This Skill freezes the unfinished session's state into a compact handoff note so a fresh session can resume without re-paying the context cost or asking the user to retell what the repository already records. ## Core Features & Use Cases - Structured handoff note: Writes a Markdown file with ordered sections (Goal, Current state, Decisions, Files touched, Proven, Next step, Open questions, Resume), each naming paths, commands, and line ranges instead of pasting content. - Git-scoped storage: A helper script computes the handoff path inside the repository's git directory keyed by branch, so linked worktrees never overwrite each other's notes, with a config-directory fallback outside git repositories. - Safe-boundary protocol: Commits uncommitted edits as a wip: commit on non-default branches before writing, and preserves verbatim any artefact the user asked to survive the clear. - Recovery without a note: A reference guide reconstructs working context from git log, diffs, and open PRs/issues when no handoff exists. - Use Case: You are mid-refactor on a feature branch with three uncommitted files and a failing test. Invoke the handoff skill, and the next session opens the note, sees the proven claims and the exact next step, and resumes at the right task. ## Quick Start Ask the AI to save this session's state with the handoff skill before running /clear, noting what the next session must not lose.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I save Claude Code session state before clearing context?▼

Invoke the handoff skill with a note about what the next session must not lose. It writes a structured Markdown file covering goal, current state, decisions, proven claims, and one next step, then tells you to run /clear.

Where are handoff notes stored in a git repository?▼

Handoff notes live inside the repository's git directory under exo/handoff, keyed by branch name, so linked worktrees each keep their own note. Outside a git repository the path falls back to the config directory keyed by the working directory name.

What is the difference between a handoff note and a plan?▼

A handoff records an unfinished session's state for the same user resuming after a clear, while a plan is a specification another executor runs. The handoff skill explicitly defers plan-style work to the planning skill and finished work to commits and pull requests.

Can I resume work if no handoff note exists?▼

Yes. The skill's reference guide reconstructs context from git status, git log, the diff against base, and open PRs and issues via gh. Facts read from git or the forge outrank inferences, and uncovered gaps become open questions.

Why does the handoff note avoid pasting diffs and file contents?▼

Pasting content spends the context the clear was meant to free. Each section names a path, command, issue number, or line range instead, since the resuming session can open those artifacts directly.