handoff

Generates a structured session handoff document capturing git state, TDD phase, and decisions for session resumption.

3|Updated Jul 2, 2026
One-click install
npx skills add https://github.com/ArangoGutierrez/claude-toolkit --skill handoff-arangogutierrez
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/ArangoGutierrez/claude-toolkit/tree/main/.claude/skills/handoff
Command: npx skills add https://github.com/ArangoGutierrez/claude-toolkit --skill handoff-arangogutierrez

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Ending a Claude Code session loses context — branch state, modified files, TDD progress, and design decisions — forcing the next session to rediscover everything. This Skill assembles a complete handoff document so a fresh session resumes with full context. ## Core Features & Use Cases - Automated context gathering: Collects active worktree, branch, modified files, and the most recent TDD phase and iteration markers from the conversation. - Transcript-based decision extraction: Dispatches a subagent to read the session JSONL transcript and summarize architectural decisions, with a graceful UNAVAILABLE fallback if the transcript cannot be located. - Epic-launch mode: /handoff --epic produces an autonomous-execution brief with mission, verified ground truth, execution loop, constraints, and ordered first actions for multi-PR epics. - Use Case: Before pausing a long debugging session, run /handoff to write a timestamped document to ~/.claude/audit/handoffs/ and paste it into your next session to pick up exactly where you left off. ## Quick Start Ask the assistant to run /handoff to generate a session handoff document you can paste into your next session.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I create a session handoff in Claude Code?▼

Run /handoff explicitly at the end of a session. It gathers git state, scans for TDD markers, extracts decisions from the session transcript via a subagent, asks what the next session should do, and writes a timestamped document to ~/.claude/audit/handoffs/.

What is the difference between /handoff and /handoff --epic?▼

A standard handoff answers 'what was I doing' for session resumption. The --epic mode produces an epic-launch brief for autonomous multi-PR execution, adding mission definition, verified ground truth, an execution loop, constraints, and ordered first actions.

What happens if the session transcript cannot be found?▼

The handoff is not blocked. Decision extraction is skipped and a placeholder is inserted asking you to manually summarize decisions, while the rest of the document — git state, files, next steps — is still assembled and printed.

When should I not use the handoff skill?▼

Do not use it when merely finishing a task, milestone, or PR, or because context usage feels high. It is only for explicit user-requested session endings; mid-task handoffs create noise, and autonomous runs should continue to the next task instead.

How accurate is the TDD phase detection in handoffs?▼

TDD phase and iteration parsing is heuristic — it scans visible conversation for [RED], [GREEN], [REFACTOR], and [Iteration X/Y] markers, so false negatives occur. You should manually correct the handoff document if the detection misses.