create-handoff

Generate YAML-frontmatter handoff documents to transfer work context between agent sessions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams transfer context between agents by generating comprehensive handoff documents that capture task status, references, and next steps for seamless continuation.

Core Features & Use Cases

  • Generate standardized handoff templates with metadata (date, repo, task, and references).
  • Create structured handoff content for handoff between sessions, agents, or teams.
  • Provide clear artifacts and action items to minimize context-switching and rework.

Quick Start

Create a handoff document detailing current work-in-progress and next steps.

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 handoff document for transitioning tasks between agent sessions?

To create a handoff document for transitioning tasks between agent sessions, this Skill automates generating structured files with metadata, file paths, YAML frontmatter, and task status to ensure seamless continuation of work context.

What is a structured handoff doc and when do I need one for project communication?

A structured handoff doc captures task status, references, and next steps for project communication. You need one during end-of-session closures or ongoing work transitions to minimize context-switching and rework between teams.

How do I generate a handoff template with YAML frontmatter for my repository?

You generate a handoff template with YAML frontmatter by running a reproducible workflow that defines metadata like date, repo, and task references, then writes the structured content and syncs changes via the HumanLayer tool.

Does this handoff doc generation workflow work for ongoing work transitions across different teams?

Yes, this handoff doc generation workflow applies to handoff scenarios across projects, sessions, and teams, including ongoing work transitions, by providing clear artifacts and action items for seamless context transfer.

What's the best way to automate end-of-session closures and task transitions?

The best way to automate end-of-session closures and task transitions is using a reproducible workflow that generates standardized handoff documents capturing work-in-progress, references, and next steps for the next agent or team.

Can I use this task-transition workflow without any external dependencies?

Yes, you can use this task-transition workflow without external dependencies. It operates independently to generate metadata, determine file paths, write YAML-frontmatter handoffs, and sync changes via the HumanLayer tool.