handoff

Generate structured session handoff documents and paste-ready kickoff prompts for context continuity.

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/ByronWilliamsCPA/plugin --skill handoff-byronwilliamscpa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/ByronWilliamsCPA/plugin/tree/main/plugins/wff-code/skills/handoff
Command: npx skills add https://github.com/ByronWilliamsCPA/plugin --skill handoff-byronwilliamscpa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a coding session ends, the next session loses all context: goals, decisions, failing tests, and dead ends. This Skill captures the full session state into a durable handoff document plus a compact kickoff prompt so work resumes without re-discovery. ## Core Features & Use Cases - Two-artifact design: Writes a full handoff doc to ~/.claude/logs/handoffs/ and prints a lean (<=200 word) kickoff prompt to paste into the new session. - Structured template: Captures goal, current git state, completed work with file:line references, remaining tasks, key decisions, dead ends, and resume steps. - Self-verification: Runs a Python pre-flight check that validates all required sections exist and enforces style rules before reporting completion. - Use Case: At the end of a long debugging session on a feature branch, run the handoff to record the failing test names, the rejected approaches, and the exact next command, then paste the kickoff prompt into tomorrow's session. ## Quick Start Ask the AI to create a session handoff so the next session can resume where this one left off.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I hand off a coding session to a new session without losing context?▼

Run the handoff workflow, which gathers git branch, status, and recent commits, then writes a full handoff document to ~/.claude/logs/handoffs/ and prints a short kickoff prompt. Paste only the kickoff prompt into the new session; it reads the full doc on demand.

What should a session handoff document include?▼

It should include the goal, current git and test state with verbatim error messages, completed work with file:line references, remaining tasks ordered by priority, key decisions with rationale, dead ends, user constraints, and exact resume steps.

Where are handoff files stored and are they committed to git?▼

Handoff files are written to ~/.claude/logs/handoffs/ with a timestamped filename. This is a durable, gitignored runtime path that is never committed and survives worktree removal.

Can I trust a handoff document as current truth when resuming?▼

No. A handoff is a snapshot from when it was written. Re-verify current state first with git fetch --all and gh pr list, treat the remaining-work section as a hypothesis, and verify any identifiers against live source before building.

Why does the handoff skill split output into a prompt and a full document?▼

The kickoff prompt is budgeted under 200 words so a new session starts lean without re-bloating its context. The full document stays on disk and is read on demand only when detail is needed.