source-command-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-create-handoff-redblacktree
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: source-command-create-handoff
Source: https://github.com/redblacktree/fastflow/tree/main/.agents/skills/source-command-create-handoff
Command: npx skills add https://github.com/redblacktree/fastflow --skill source-command-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 markdown handoff document so another agent or session can resume seamlessly. ## Core Features & Use Cases - Standardized Handoff Documents: Generates markdown files with YAML frontmatter (date, git commit, branch, repository, status) and structured sections for tasks, learnings, artifacts, and next steps. - Consistent File Naming: Places documents under thoughts/shared/handoffs/ with timestamped, ticket-aware filenames like 2025-01-08_13-55-22_ENG-2166_create-context-compaction.md. - Metadata Automation: Runs scripts/spec_metadata.sh to gather git and session metadata, then syncs via humanlayer thoughts sync. - Use Case: Before ending a long debugging session on ticket ENG-2166, invoke this Skill to produce a handoff summarizing recent changes, root causes found, and remaining action items, then resume later with /resume_handoff. ## Quick Start Ask the agent to create a handoff document for the current session so the work can be resumed in a new session.

Frequently Asked Questions about source-command-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 create_handoff command, which writes a markdown file under thoughts/shared/handoffs with YAML frontmatter and sections for tasks, changes, learnings, and next steps. Resume later with /resume_handoff followed by the document path.

What should a handoff document include for another agent?▼

Include task statuses, critical reference documents, recent code changes in file:line format, key learnings, an artifact list, and action items. The Skill provides a template covering all of these sections with YAML metadata.

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

Handoffs are stored under thoughts/shared/handoffs/ENG-XXXX/ with filenames combining date, 24-hour time, ticket number, and a kebab-case description, such as 2025-01-08_13-55-22_ENG-2166_create-context-compaction.md.

Does the handoff skill work without a ticket number?▼

Yes. When no ticket exists, the directory uses 'general' and the ticket segment is omitted from the filename, producing names like 2025-01-08_13-55-22_create-context-compaction.md.

Why should handoffs avoid large code snippets?▼

Large code blocks bloat the document and duplicate repository content. The Skill recommends file:line references like packages/dashboard/src/app/page.tsx:12-24 so the next agent can read exact code on demand.