skills.rest
tfunk1030
tfunk1030COMMUNITY
Explore all skills by this author →
GitHub

create_handoff

Generate structured handoff documents with YAML frontmatter for Claude sessions.

1|Updated Jan 2, 2026
Search Tags:#workflow#documentation#metadata#handoff#braintrust#session-transfer
One-click install
npx skills add https://github.com/tfunk1030/vibe --skill create-handoff-tfunk1030
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create_handoff
Source: https://github.com/tfunk1030/vibe/tree/main/.claude/skills/create_handoff
Command: npx skills add https://github.com/tfunk1030/vibe --skill create-handoff-tfunk1030

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Handoff work between Claude sessions by generating a thorough, concise handoff document that preserves context and key details for a seamless transition.

Core Features & Use Cases

  • Automatic session metadata extraction and file path generation based on the active ledger.
  • YAML frontmatter assembly with required fields (date, session_name, researcher, git_commit, branch, repository, topic, tags, status) and a structured body describing the handoff.
  • Guidance for Braintrust trace linking and artifact indexing to ensure traceability across sessions.
  • Clear post-handoff procedures including how to mark outcomes and resume work in a new session.

Quick Start

Create a new handoff file under thoughts/shared/handoffs using the active session name and run the metadata script to populate it.

Frequently Asked Questions about create_handoff

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

FAQPage Schema
How do I generate a session handoff document for transferring work between Claude sessions?▼

To generate a session handoff document, create a file under thoughts/shared/handoffs using the active session name, then run the metadata script to populate it with required YAML frontmatter and a structured body for seamless session transfers.

What metadata is required for a structured handoff document?▼

A structured handoff document requires YAML frontmatter with date, session_name, researcher, git_commit, branch, repository, topic, tags, and status, ensuring complete context preservation for the receiving agent.

How do I track artifacts and next steps when wrapping up a Claude session?▼

You track artifacts and next steps by generating a handoff document that includes a formatted body for artifact tracking, actionable handoff tasks, and references to the artifact-index workflow for traceability.

Does this handoff workflow support Braintrust trace linking and git metadata?▼

Yes, the handoff workflow extracts git metadata like branch and commit hash for YAML frontmatter, and provides explicit guidance for Braintrust trace linking to ensure traceability across sessions.

What is the best way to document session wrap-ups for a new agent?▼

The best way to document session wrap-ups is generating a thorough handoff document that preserves context through metadata, a narrative summary, and actionable next steps for a new agent to resume work.

What should I do to resume work in a new session after creating a handoff document?▼

After creating a handoff document, follow the guided post-handoff procedures to mark outcomes and reference the generated file to resume work seamlessly in a new session.

Related Skills

Explore More Content & Communication Skills→
joaquimscostajoaquimscosta
21

creating-branch

Create standardized Git feature branches with incrementing names.

Community
Advanced
BrightBlockBrightBlock
2

create_handoff

Generate a standardized handoff document with frontmatter and next steps.

Official
Advanced
ramonclaudioramonclaudio
4

end

Archive Claude session state and health checks to the .handoff directory.

Community
Advanced
h4vzzh4vzz
33

note-taking

Create, organize, and retrieve Markdown notes with YAML metadata and tags.

Community
Intermediate