handoff

Generates a session handoff document capturing goals, decisions, and next steps for another agent.

Updated May 13, 2026
One-click install
npx skills add https://github.com/andrewcodesit/skills --skill handoff-andrewcodesit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/andrewcodesit/skills/tree/main/skills/project-management/handoff
Command: npx skills add https://github.com/andrewcodesit/skills --skill handoff-andrewcodesit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an agentic coding session ends, all context about goals, decisions, and unfinished work disappears, forcing the next session to start from zero. This Skill captures the full session state into a self-contained Markdown handoff document that another agent can act on without asking clarifying questions. ## Core Features & Use Cases - Context Gathering: Collects repo name, active branch, uncommitted changes, recent commits, existing plans, and the full conversation history before writing anything. - Structured Handoff Template: Produces a standardized document with Goal, Current State, Decisions Made, Next Steps, Open Questions, Key Files, Constraints, and Environment Notes sections. - Use Case: You spent a session halfway through an auth refactor and need to stop. Run the handoff command, and the next agent receives a document at ~/.agents/handoffs/<repo>-<date>-auth-refactor.md telling it exactly what was done, why, and what to do first. ## Quick Start Ask the agent to generate a handoff doc for the current session so the next agent can continue the work.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I hand off an unfinished coding session to another AI agent?▼

Run the handoff command at the end of your session. It gathers git status, recent commits, conversation decisions, and open questions, then writes a structured Markdown document the next agent can read to continue exactly where you stopped.

What should a good agent handoff document include?▼

A handoff document should include the goal with acceptance criteria, current state including uncommitted changes, decisions made with reasoning, ordered next steps naming specific files, open questions, key files, and constraints or gotchas discovered during the session.

Where are handoff documents saved?▼

Handoff documents are saved to ~/.agents/handoffs/ with a filename combining the repo name, date, and a short kebab-case slug, such as myrepo-2024-01-15-auth-refactor.md. Outside a git repo, scratch is used as the repo name.

Does the handoff skill work outside a git repository?▼

Yes, it works outside git repositories by using scratch as the repo name and noting no git in the branch field. Git-specific sections like branch and uncommitted changes are simply reported as unavailable.

When should I create a handoff instead of just continuing later?▼

Create a handoff whenever a session ends with unfinished work, when switching between agents or tools, or when another person or agent will pick up the task. It prevents re-litigating settled decisions and losing context about half-done changes.