skills.rest
stefanfaur
stefanfaurCOMMUNITY
Explore all skills by this author →
GitHub

create-handoff

Creates structured handoff documents to transfer session context between work sessions.

1|Updated Feb 10, 2026
Search Tags:#workflow#documentation#markdown#session management#knowledge transfer#handoff#context transfer
One-click install
npx skills add https://github.com/stefanfaur/roach-marketplace --skill create-handoff-stefanfaur
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-handoff
Source: https://github.com/stefanfaur/roach-marketplace/tree/main/roach/skills/create-handoff
Command: npx skills add https://github.com/stefanfaur/roach-marketplace --skill create-handoff-stefanfaur

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long AI-assisted work sessions lose context when they end or hit context limits, forcing the next session to rediscover decisions, file changes, and next steps. This Skill captures that state in a structured Markdown handoff document before context is lost. ## Core Features & Use Cases - Structured Context Capture: Writes a handoff file with tasks, critical references, recent changes, learnings, artifacts, and action items using a defined YAML frontmatter schema. - Domain-Scoped Storage: Saves handoffs to thoughts/shared/handoffs/<domain>/ with timestamped filenames for organized retrieval. - Metadata Automation: Runs a helper script to collect date, git commit, branch, and repository metadata for the document. - Use Case: Before ending a long debugging session on a payment feature, create a handoff so the next session can resume with /roach:resuming-handoff and immediately continue from the current plan phase. ## Quick Start Ask the assistant to create a handoff for the current session before pausing or ending your work.

Frequently Asked Questions about create-handoff

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

FAQPage Schema
How do I transfer context between Claude Code sessions?▼

Create a handoff document before ending the session. It captures tasks, recent changes, learnings, and next steps in a structured Markdown file, which a new session resumes using the resuming-handoff command with the file path.

When should I create a handoff document?▼

Create one proactively when context is growing long, before pausing mid-task, when ending a session with unfinished work, or when handing off to another agent. Do not wait for auto-compaction, which loses structured detail.

Where are handoff files stored?▼

Handoffs are saved under thoughts/shared/handoffs/<domain>/ with a timestamped filename like YYYY-MM-DD_HH-MM-SS_description.md. The domain is detected from task context, such as accrual, kpi, or general.

What information does a handoff document include?▼

It includes YAML metadata (date, git commit, branch, repository, topic, status) plus sections for tasks with status, critical file references, recent changes, learnings, artifacts, action items, and other notes.

Is a handoff better than auto-compaction?▼

Yes. Auto-compaction compresses context lossy, while a handoff preserves richer, structured context with explicit file:line references and action items that a new agent can immediately act on.

Related Skills

Explore More Software Engineering Skills→
visualityplvisualitypl
4

create_handoff

Generate structured handoff documents with YAML frontmatter for AI session transfers.

Official
Intermediate
visualityplvisualitypl
4

resume_handoff

Analyze handoff documents and validate previous work against the current codebase.

Official
Advanced
jeffhjeffh
12

spec-metadata

Generate timestamped Git metadata as YAML frontmatter for research documents.

Community
Basic
bhaumikmaanbhaumikmaan
3

session-handoff

Generate structured session handoff notes with fixed templates and token budgets.

Community
Advanced