handoff

Generate a Markdown handoff document with branch, status, and next steps.

2|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/leocaseiro/base-skill --skill handoff-leocaseiro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/leocaseiro/base-skill/tree/main/.claude/skills/handoff
Command: npx skills add https://github.com/leocaseiro/base-skill --skill handoff-leocaseiro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a session handoff document so work can continue in a new session or with another agent. Use when just saved a plan or spec, just raised or merged a PR, ending a work session, context-switching, or explicitly told to hand off / continue later. Triggers on phrases like "hand this off", "continue in a new session", "pick this up later", "end of session", "wrap up".

Core Features & Use Cases

  • Auto-detect context within the active worktree and scaffold a handoff prefill.
  • Generate a structured Markdown handoff with metadata (date, branch, path, last commit, PR status) and a concise recap of decisions and next steps.
  • Save the document under .claude/handoffs/YYYY-MM-DD-<slug>.md and commit as a baby step to preserve history.

Quick Start

Ask Claude to generate a handoff document for the current worktree and save it under .claude/handoffs.

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 document to continue work later?

To create a session handoff document, this Skill auto-detects your active worktree context and generates a structured Markdown file under .claude/handoffs. It prefills metadata like branch, path, status, and next steps, then commits the file to preserve your workflow history.

What is the best way to transfer work context between agents or sessions?

Transferring work context between agents requires a structured handoff document capturing decisions and next steps. This Skill scaffolds a Markdown template tailored to your current branch and last commit, ensuring another agent can seamlessly pick up the work.

How do I trigger an automated workflow handoff when ending a session?

You can trigger an automated workflow handoff by using phrases like "hand this off", "wrap up", or "continue in a new session". The Skill detects these triggers, prompts for key decisions, and writes a baby-step commit to save the handoff document.

Can I save a handoff document with my current branch and PR status?

Yes, you can save a handoff document with your current branch and PR status. The Skill auto-fills a Markdown template with the active worktree path, last commit, and PR status, saving it directly under the .claude/handoffs directory.

Does team collaboration documentation work without extra dependencies?

Team collaboration documentation works without extra dependencies. The Skill operates independently to generate Markdown handoff skeletons and commit them directly to your repository, requiring no external libraries or components.

What should a handoff document include to preserve work history?

A handoff document should include the date, active branch, worktree path, last commit, PR status, a concise recap of decisions, and next steps. This Skill automatically structures these elements into a Markdown file and commits it as a baby step.