handoff

Writes and resumes HANDOFF.md files preserving session state across context clears.

2|Updated May 13, 2026
One-click install
npx skills add https://github.com/curtisgalloway/public-skills --skill handoff-curtisgalloway
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/curtisgalloway/public-skills/tree/main/plugins/agent-workflow/skills/handoff
Command: npx skills add https://github.com/curtisgalloway/public-skills --skill handoff-curtisgalloway

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an AI coding session is cleared, compacted, or restarted, all working context—task intent, decisions, failed approaches, and verbal instructions—is lost. This Skill captures that state in a HANDOFF.md file so the next session can resume work as if the interruption never happened. ## Core Features & Use Cases - Write mode: Dumps a structured HANDOFF.md at the project root covering task, state, decisions, dead ends, next steps, and standing user instructions, then excludes it from git via .git/info/exclude. - Resume mode: Reads the handoff, verifies branch and SHA against current repo state to detect drift, consumes the file by renaming it to HANDOFF.md.read, and continues the work. - Automatic mode detection: With no argument, infers write vs. resume from whether an unconsumed HANDOFF.md exists at the project root. - Use Case: Before ending a long debugging session, run /handoff to record the exact failing test, the two approaches already ruled out, and the next command to try; the next morning a fresh session resumes with full context. ## Quick Start Ask the agent to run /handoff before clearing the context so it writes a HANDOFF.md the next session can resume from.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I preserve AI session context before clearing it?▼

Run /handoff before clearing. It writes a HANDOFF.md at the project root capturing the task, current state, decisions, dead ends, and next steps, so the next session can cold-start from that file.

How do I resume work from a previous agent session?▼

Start a new session and invoke /handoff with no argument, or ask the agent to read the handoff. It reads HANDOFF.md, verifies the recorded branch and SHA against current repo state, then continues from the first next step.

Will HANDOFF.md show up in git status or get committed?▼

No. The skill appends HANDOFF.md* to .git/info/exclude, keeping the handoff and its consumed .read form out of git status without modifying the repo's tracked .gitignore.

What happens if the repo changed since the handoff was written?▼

Resume mode compares the recorded branch and short SHA against current state and checks git status. Any drift is reported to the user rather than silently proceeding on stale assumptions.

What should not go into a handoff file?▼

No secrets: tokens, passwords, and internal hostnames must never appear since the file is plaintext at the project root. Also omit anything recoverable from git log or the code itself; record only intent, rationale, and failures.