parcadei-create-handoff

Create dated YAML handoff documents with goals, context, and next steps.

2|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/anyekoutouming/anyekoutouming --skill parcadei-create-handoff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: parcadei-create-handoff
Source: https://github.com/anyekoutouming/anyekoutouming/tree/main/parcadei-create-handoff
Command: npx skills add https://github.com/anyekoutouming/anyekoutouming --skill parcadei-create-handoff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps generate a thorough but concise handoff document to transfer work to another agent or session.

Core Features & Use Cases

  • Auto-detect the target session from the most recently modified handoff folder, or use "general" if none exists.
  • Create a standardized file at thoughts/shared/handoffs/{session-name}/YYYY-MM-DD_HH-MM_description.yaml with today's date and a kebab-case title.
  • Populate YAML frontmatter with date and session_name and provide a structured body to capture goals, context, artifacts, decisions, and next steps.

Quick Start

Run the handoff creation flow to generate thoughts/shared/handoffs/{session-name}/YYYY-MM-DD_HH-MM_description.yaml and populate it with the session context.

Frequently Asked Questions about parcadei-create-handoff

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

FAQPage Schema
How do I create a handoff document for transferring agent session context?

To create a handoff document, the skill generates a YAML file at a standardized path using the target session name and timestamp, then populates the body with goals, context, artifacts, decisions, and next steps for the next agent.

What is the best way to structure session transfers between multiple agents?

The best way to structure session transfers is using a standardized YAML format that captures goals, context, artifacts, decisions, and next steps, ensuring the next agent receives complete workflow continuity.

How does session management determine the target handoff folder?

Session management determines the target handoff folder by auto-detecting the most recently modified handoff folder within the thoughts/shared/handoffs/ directory, defaulting to 'general' if none exists.

Do I need to manually name handoff files when documenting workflow state?

You do not need to manually name handoff files. The skill automatically generates a kebab-case description title and appends the current date and time in a YYYY-MM-DD_HH-MM format to the filename.

Can I use YAML frontmatter to track session metadata for artifact indexing?

You can use YAML frontmatter to track session metadata by automatically populating the date and session_name fields, which supports artifact indexing and organizes workflow documentation for future retrieval.

What limitations exist when auto-detecting a session name for handoff documentation?

A key limitation is that auto-detection relies entirely on existing folder modification times within the handoffs directory, meaning it will default to a generic session name if no prior handoff folders are present.