handoff

Capture in-flight project context into durable handoff documents.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/ChazzCoin/claude-kit --skill handoff-chazzcoin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/ChazzCoin/claude-kit/tree/main/kit/skills/handoff
Command: npx skills add https://github.com/ChazzCoin/claude-kit --skill handoff-chazzcoin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Snapshot in-flight project context into a durable handoff doc so teammates can pick up where you left off without losing threads.

Core Features & Use Cases

  • Auto-generate a comprehensive handoff document from current state (branches, working tree, in-flight tasks, decisions, blockers, postmortems) into docs/handoff/<YYYY-MM-DD>.md.
  • Create a concise welcome note at .claude/welcome.md to surface critical next steps on session start.
  • Suitable for mid-project handoffs, leave scenarios, or when handing off a project to a teammate.

Quick Start

Run the /handoff command to snapshot your in-flight state into a full handoff document and a concise welcome note.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I document in-flight project context for a smooth handoff?

To document in-flight project context for a handoff, run the /handoff command to snapshot branches, tasks, and decisions into a durable markdown file. This aggregates your working state into a structured document without making source edits or commits.

What is the best way to onboard new contributors to a mid-project workflow?

The best way to onboard new contributors is to generate a comprehensive handoff document alongside a concise welcome note. This captures current git state and blockers, surfacing critical next steps at session start so teammates immediately understand the project context.

How does knowledge transfer during leaves or transitions work without altering source code?

Knowledge transfer during leaves works by aggregating in-flight tasks and postmortems into durable markdown docs. It captures the project context into specific output paths without editing source files or creating git commits, ensuring a clean working tree.

Can I capture git state and decisions without making commits?

Yes, you can capture git state and decisions without making commits. The process specifically avoids source edits and commits, directing the aggregated project context exclusively into markdown documentation files for safe knowledge transfer.

Where does the generated project context and welcome note get saved?

The generated project context is saved to dated markdown files within the docs/handoff directory, while the concise welcome note is placed at .claude/welcome.md. This ensures teammates find critical next steps immediately upon starting a session.