create-handoff

Create a structured handoff document with Git metadata and task sections.

1|1|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/corticalstack/claude-code-flow --skill create-handoff-corticalstack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-handoff
Source: https://github.com/corticalstack/claude-code-flow/tree/main/.claude/skills/create-handoff
Command: npx skills add https://github.com/corticalstack/claude-code-flow --skill create-handoff-corticalstack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents lost context when switching to another agent by producing a structured, resume-ready handoff document that captures what was done, what changed, and what to do next.

Core Features & Use Cases

  • Structured handoff file creation: Writes a thorough but concise document under flow/handoffs/ using a consistent, timestamped naming convention.
  • Session context capture: Includes Git metadata (commit hash, branch, repository) and organizes work into Task(s), Critical References, Recent changes, Learnings, and Artifacts.
  • Explicit-only workflow: Designed to run only when invoked via /create-handoff or when the user requests a handoff, ensuring it does not interrupt other work.

Quick Start

Use /create-handoff to generate a handoff document that another agent can resume from in a new session.

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 to transfer work context to another AI agent?

To create a handoff document, invoke the /create-handoff command. This generates a structured, resume-ready file under flow/handoffs/ that captures completed tasks, recent changes, and next steps for another agent to resume.

What is an agent handoff document and when do I need one for my workflow?

An agent handoff document is a structured file that transfers current work context to another agent for continued execution. You need one when switching to a new session to prevent lost context and ensure work continuity.

What Git metadata and session context is included in a structured handoff file?

A structured handoff file includes Git metadata like the commit hash, branch, and repository. It also organizes session context into sections for Tasks, Critical References, Recent changes, Learnings, Artifacts, and Next Steps.

Does the create-handoff workflow run automatically during my development session?

No, the create-handoff workflow runs only on explicit invocation. It is designed to execute solely when triggered via the /create-handoff command or a direct user request, ensuring it does not interrupt other work.

Can I use this handoff workflow for general development tasks or only for AI-assisted sessions?

You can use this handoff workflow for both general development and AI-assisted workflows. It applies to any scenario where work must be handed off between sessions, summarizing completed and in-progress tasks.

What is the best way to summarize task status and learnings before switching agents?

The best way to summarize task status and learnings is to generate a structured handoff document. This file captures your current work context, including recent changes and learnings, ensuring the next agent can resume execution immediately.