skills.rest
juicesharp
juicesharpCOMMUNITY
Explore all skills by this author →
GitHub

create-handoff

Generate a Markdown handoff document with YAML frontmatter and repository metadata.

581|102|Updated Apr 18, 2026
Search Tags:#documentation#markdown#handoff#git-metadata#knowledge-transfer#context-preservation#session-transition
One-click install
npx skills add https://github.com/juicesharp/rpiv-mono --skill create-handoff-juicesharp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-handoff
Source: https://github.com/juicesharp/rpiv-mono/tree/main/packages/rpiv-pi/skills/create-handoff
Command: npx skills add https://github.com/juicesharp/rpiv-mono --skill create-handoff-juicesharp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The handoff creation process helps you compact and preserve essential context when transitioning between sessions, reducing repetition and miscommunication.

Core Features & Use Cases

  • Generate a compact handoff document that captures repository context (repository, branch, commit) and task state.
  • Include key decisions, dependencies, and action items to ensure continuity across sessions.
  • Use Case: When starting a new session after a long research phase, generate a handoff to summarize work and next steps for the next agent.

Quick Start

Create a handoff document at thoughts/shared/handoffs/YYYY-MM-DD_HH-MM-SS_description.md using the current repository and session metadata.

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 context-preserving handoff for a repository session transition?▼

A session handoff document compacts essential context into a Markdown file with YAML frontmatter, capturing repository name, branch, commit, and a narrative of decisions. This preserves task state to prevent repetition during session transitions.

What repository metadata should a knowledge-transfer handoff include?▼

A knowledge-transfer handoff should include repository name, branch, commit, researcher, timestamp, and a brief narrative of decisions. Capturing this git metadata ensures continuity and preserves context across session transitions.

How do I structure a markdown handoff document for agent continuity?▼

Structure the markdown handoff with YAML frontmatter containing at least name and description, followed by a Markdown body for operational instructions. Optional structured artifacts directories can hold scripts, references, and assets.

When do I need to generate a handoff document for my workflow?▼

You need to generate a handoff document when starting a new session after a long research phase. It summarizes work and next steps, reducing miscommunication and enabling the next agent to resume smoothly.

Does the handoff creation process support structured directories for scripts and references?▼

Yes, the handoff creation process supports optional structured artifacts directories for scripts, references, and assets. These directories organize supplementary materials alongside the main markdown handoff document.

Related Skills

Explore More Content & Communication Skills→
jeffhjeffh
12

spec-metadata

Generate timestamped Git metadata as YAML frontmatter for research documents.

Community
Basic
theomonforttheomonfort
3

create-handoff

Generate timestamped Markdown handoff documents with Git metadata.

Community
Intermediate
Monjyu1101Monjyu1101
1

hermes-agent-skill-authoring

Author in-repo Hermes-Agent skills with validated YAML frontmatter and Markdown bodies.

Community
Advanced
lastmjslastmjs

episode-generate-metadata

Generate title, notes, and keywords from podcast episode text into JSON.

Community
Basic