handoff

Packages project state into structured handoff documents for agent sessions and human pickup.

4|2|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/Arete-Consortium/ai-skills --skill handoff-arete-consortium
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/Arete-Consortium/ai-skills/tree/main/agents/analysis/handoff
Command: npx skills add https://github.com/Arete-Consortium/ai-skills --skill handoff-arete-consortium

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Context loss between work sessions forces every new AI agent session or returning developer to re-read files, re-discover decisions, and re-establish intent. This Skill captures git state, plan files, and project conventions into a structured handoff document so the next session starts immediately. ## Core Features & Use Cases - Audience-Specific Formats: Generates handoffs optimized for AI agents, humans, or Quorum IntentNodes for inter-agent coordination. - Automatic Context Gathering: Reads git status, recent commits, branch, uncommitted changes, .claude/plans/, and CLAUDE.md without manual input. - Handoff Lifecycle Management: Create, list, and update handoff documents stored in .claude/handoffs/ with timestamped naming. - Use Case: Before ending a coding session on a feature branch with uncommitted changes, generate an agent handoff that records the exact next action, modified files, and open questions so the next Claude Code session resumes without re-exploration. ## Quick Start Ask the agent to create a handoff for the current project before ending this session, specifying whether the audience is an agent, a human, or a Quorum IntentNode.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I create a handoff document for the next Claude Code session?▼

Invoke the create_handoff operation with an intent stating who picks up the work. The agent reads git status, recent commits, plan files, and CLAUDE.md, then writes a timestamped document to .claude/handoffs/ with a specific immediate next action.

What is the difference between agent, human, and quorum handoff formats?▼

The agent format is structured for immediate AI session resumption, the human format uses plain-language summaries for returning developers, and the quorum format maps sections to IntentNode fields for inter-agent coordination in Convergent/Quorum systems.

Where are handoff documents stored and can I list existing ones?▼

Handoffs are stored in .claude/handoffs/ with the naming pattern handoff-[date]-[audience].md. Use the list_handoffs operation to enumerate existing documents, and update_handoff to revise one by slug.

Does the handoff skill work outside a git repository?▼

Yes. When the project is not a git repository, the agent skips git sections and notes the absence in the handoff. Missing plan files or CLAUDE.md are handled the same way with explicit notes.

When should I not use a session handoff document?▼

Do not use handoffs for permanent project documentation, long-term memory across many sessions, or git commits and changelogs. Handoffs are ephemeral single-session state snapshots under 500 lines.