create-handoff

Generate a structured handoff document with YAML frontmatter and content template.

Updated Aug 23, 2026

Search Tags:#workflow #documentation #resume #handoff #frontmatter #session-context #knowledge-transfer

Ready to run

npx skills add https://github.com/ncy08/clear-claude-code --skill create-handoff-ncy08

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-handoff
Source: https://github.com/ncy08/clear-claude-code/tree/main/tools/skills/create-handoff
Command: npx skills add https://github.com/ncy08/clear-claude-code --skill create-handoff-ncy08

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams and agents document the end-of-session handoff, preserving context so a future agent can resume work with minimal friction.

Core Features & Use Cases

Generate a structured handoff with metadata (date, git commit, branch, repository, topic, status, last_updated) and content body.
Enforce a standardized file path and YAML frontmatter, including optional sections for references and learnings.
Use when ending a long work session, handing off to a new agent, or resuming work in a future session.

Quick Start

Create the handoff using the specified path and frontmatter schema to capture the session context.

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 session handoff document for resuming work later?▼

To create a session handoff document, you capture metadata like git branch, commit, and status into a YAML frontmatter schema, then document the task, references, learnings, and next steps in the body template.

What is a session handoff document used for in cross-session workflows?▼

A session handoff document is used for knowledge transfer, preserving the context of long work sessions so a future agent can resume resumable tasks with minimal friction and immediate clarity.

What metadata should I include in a YAML frontmatter handoff file?▼

Include metadata such as date, git commit, branch, repository, topic, status, and last_updated in your YAML frontmatter to ensure the handoff file provides complete session context for future resumption.

Does a handoff document template support custom sections for learnings and references?▼

Yes, the handoff document template enforces a structured body and YAML frontmatter schema while supporting optional sections specifically for capturing references and learnings during knowledge transfer.

Can I use frontmatter handoff documents for team knowledge transfer instead of just agent sessions?▼

Yes, you can use frontmatter handoff documents for team knowledge transfer, as they standardize file path conventions and content structure to preserve context for both human teammates and future agents.

What is the best way to structure session context before ending a long work session?▼

The best way to structure session context is applying a standardized file path and YAML frontmatter schema, then organizing the body into task details, references, learnings, and next steps.