create_handoff

Name: create_handoff
Availability: InStock
Author: parcadei

Generate structured handoff documents with YAML frontmatter and session metadata.

3.9k|296|Updated Dec 23, 2025

Search Tags:#workflow #planning #documentation #handoff #handoff-file

Ready to run

npx skills add https://github.com/parcadei/Continuous-Claude --skill create-handoff

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create_handoff
Source: https://github.com/parcadei/Continuous-Claude/tree/main/.claude/skills/create_handoff
Command: npx skills add https://github.com/parcadei/Continuous-Claude --skill create-handoff

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates the creation of thorough yet concise handoff documents to transfer work between sessions or agents.

Core Features & Use Cases

Handoff templates: Generate structured handoffs with task summaries, artifacts, and learnings.
Metadata enrichment: Attach timestamps, repository info, and references to relevant files.

Quick Start

Create a handoff for the current task and save it to thoughts/shared/handoffs/<session>/YYYY-MM-DD_HH-MM-SS_description.md.

Frequently Asked Questions about create_handoff

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

FAQPage Schema

How do I create a handoff document to transfer work between sessions?▼

Create a handoff document by capturing your current task context, references, changes made, and next steps into a structured YAML file saved under thoughts/shared/handoffs. The document includes session metadata, timestamps, and organized sections for task summaries, artifacts, and learnings to enable seamless continuation by another agent.

What should I include in a handoff file for project continuity?▼

A handoff file includes task descriptions, relevant file references, a summary of changes and decisions made, key learnings, post-mortem insights, generated artifacts, and prioritized next steps. Frontmatter contains session name, timestamps, and Braintrust IDs to maintain full context across agent transitions.

When do I need to generate a handoff document?▼

Generate a handoff during session transitions, when handing off work to another agent, or upon task completion. Handoffs are essential when an active ledger exists for your continuity stream, ensuring incoming agents have complete project context without repeating work.

Can I automate handoff creation with workflow documentation?▼

Yes. Handoffs automate documentation by deriving session names from your active ledger, generating YAML metadata automatically, and structuring content into predefined sections. This reduces manual effort while ensuring consistent, thorough documentation for cross-session transfers.

What's the difference between a handoff document and general project documentation?▼

Handoff documents are concise, session-specific transfers designed for agent-to-agent continuity, with structured sections and machine-readable frontmatter. General documentation is broader; handoffs focus on immediate next steps, recent decisions, and artifacts needed to resume work without context loss.

Do I need repository information to create a handoff?▼

Yes. Handoffs enrich metadata with repository info, timestamps, and file references to ground the work in its source context. This ensures the receiving agent can locate relevant files and understand the project state at the moment of handoff.