source-command-ff-create-handoff

Creates structured handoff documents for transferring work context between agent sessions.

1|1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/redblacktree/fastflow --skill source-command-ff-create-handoff-redblacktree
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: source-command-ff-create-handoff
Source: https://github.com/redblacktree/fastflow/tree/main/.agents/skills/source-command-ff-create-handoff
Command: npx skills add https://github.com/redblacktree/fastflow --skill source-command-ff-create-handoff-redblacktree

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? When a coding session ends or context runs out, critical details about tasks, decisions, and progress are lost. This Skill captures the current state of work into a structured handoff document so another agent or session can resume seamlessly. ## Core Features & Use Cases - Structured Handoff Documents: Generates markdown handoffs with YAML frontmatter including date, git commit, branch, repository, and status metadata. - Standardized File Naming: Places documents under thoughts/shared/handoffs/ with timestamped, ticket-aware filenames. - Metadata Automation: Runs scripts/spec_metadata.sh to gather repository metadata and syncs via humanlayer thoughts sync. - Use Case: Before ending a long debugging session on ticket ENG-2166, generate a handoff capturing recent changes, learnings, artifacts, and next steps so a fresh session can resume with /ff_resume_handoff. ## Quick Start Ask the agent to create a handoff document for the current session's work so it can be resumed in a new session.

Frequently Asked Questions about source-command-ff-create-handoff

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

FAQPage Schema
How do I create a handoff document to resume work in a new session?▼

Invoke the ff_create_handoff command, which writes a structured markdown handoff under thoughts/shared/handoffs with task status, recent changes, learnings, and next steps. Resume later with /ff_resume_handoff followed by the document path.

What should a handoff document include for agent session transfer?▼

A handoff should include task statuses, critical references, recent code changes with file:line references, key learnings, produced artifacts, and action items. It uses YAML frontmatter with date, git commit, branch, and repository metadata.

Where are handoff files stored and how are they named?▼

Handoffs are stored under thoughts/shared/handoffs/ENG-XXXX/ with filenames like YYYY-MM-DD_HH-MM-SS_ENG-ZZZZ_description.md. The ticket number is omitted or replaced with 'general' when no ticket exists.

Does the handoff skill require a ticket number?▼

No, a ticket number is optional. If none exists, the directory uses 'general' and the ticket segment is omitted from the filename while all other metadata remains unchanged.

Why is my handoff not visible to other sessions after creation?▼

The document must be synced by running humanlayer thoughts sync after writing the file. Without syncing, the handoff stays local and cannot be discovered by other sessions.