handoff-create

Generate a structured Markdown handoff document with session scope and next steps.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/srednoff888-art/4 --skill handoff-create
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff-create
Source: https://github.com/srednoff888-art/4/tree/main/examples/skills/handoff-create
Command: npx skills add https://github.com/srednoff888-art/4 --skill handoff-create

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically generate a structured handoff document from the current conversation, capturing scope, key discoveries, work completed, current status, and next steps to ensure smooth transitions.

Core Features & Use Cases

  • Structured handoff document with sections for Task, Scope, Files, Discoveries, Work Done, Status, Next Steps, and Code.
  • Saves the document to claudedocs/handoffs/handoff_YYYYMMDD_HHMMSS.md by default, with an optional filename via ARGUMENTS[0].
  • Ideal for ending a session or handing work to another agent or for archival context.

Quick Start

Provide an optional filename as the first argument to customize the handoff file name and run the skill to generate the document.

Frequently Asked Questions about handoff-create

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

FAQPage Schema
How do I create a handoff document for transferring work to another agent?

To create a handoff document, this skill generates a structured Markdown file capturing the session's task, scope, files, discoveries, work done, status, and next steps. It saves the document automatically to the claudedocs/handoffs/ directory for seamless work transfer.

What is the best way to document session discoveries and next steps before ending a conversation?

Documenting session discoveries and next steps is handled by generating a structured Markdown handoff document. It automatically extracts and organizes work completed, current status, and future actions into a standardized archival format for context retention.

Can I specify a custom filename when generating a Markdown handoff document?

Yes, you can specify a custom filename for your Markdown handoff document by providing it as the first argument. Without a custom name, it defaults to a timestamped format like handoff_YYYYMMDD_HHMMSS.md in the claudedocs/handoffs/ folder.

How does automated session transfer documentation work for collaboration?

Automated session transfer documentation works by parsing the current conversation and structuring it into Markdown sections including Task, Scope, Files, Discoveries, Work Done, Status, Next Steps, and Code. This ensures another agent receives complete context without manual summarization.

Do I need any dependencies or components to generate structured Markdown handoff files?

No dependencies or components are required to generate structured Markdown handoff files. The skill operates independently to process the session and output the documentation directly to your local claudedocs/handoffs/ directory.

When should I use an automated handoff generator instead of manually writing session notes?

An automated handoff generator should be used when ending a session or transferring work to another agent, ensuring structured context without manual effort. It systematically captures scope, discoveries, and code details that manual notes might omit.