create-handoff

Writes a structured handoff document under flow/handoffs/ to transfer work between sessions.

1|1|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/corticalstack/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/flow/tree/main/.claude/skills/create-handoff
Command: npx skills add https://github.com/corticalstack/flow --skill create-handoff-corticalstack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an agentic coding session ends, all context about tasks, decisions, and progress is lost. This Skill captures that context in a structured Markdown handoff document so a new session can resume work without re-discovery. ## Core Features & Use Cases - Structured Handoff Template: Generates a Markdown document with YAML frontmatter (issue id, date, git commit, branch, repository, tags) and sections for tasks, critical references, recent changes, learnings, artifacts, and next steps. - Git Metadata Capture: Automatically gathers commit hash, branch name, and remote repository URL via git commands to anchor the handoff to the exact codebase state. - Tracker-Aware File Naming: Organizes handoffs under flow/handoffs/gh-<id>/ with timestamped kebab-case filenames, falling back to a general folder when no tracker item exists. - Use Case: Before ending a long implementation session on a streaming API, invoke the skill to produce flow/handoffs/gh-123/2025-01-08_13-55-22_implement-streaming-api.md, then resume later with /resume-handoff pointing at that file. ## Quick Start Ask the agent to create a handoff for the current work so it can be resumed 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 hand off work between AI coding sessions?▼

Invoke the create-handoff skill before ending your session. It writes a Markdown document under flow/handoffs/ capturing tasks, recent changes, learnings, artifacts, and next steps, which a new session can load with /resume-handoff.

What should a good agent handoff document include?▼

A handoff should include task status, critical reference documents, recent code changes in file:line format, key learnings, an artifact list, and action items. This skill enforces that structure through a fixed Markdown template with YAML frontmatter.

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

Handoffs are saved under flow/handoffs/gh-<id>/ using the tracker work-item id, or flow/handoffs/general/ when no tracker reference exists. Filenames combine the date, 24-hour time, and a kebab-case description.

Does the handoff skill run automatically at session end?▼

No. The skill is explicit-only with model invocation disabled, so it runs only when invoked via /create-handoff or when the user directly asks for a handoff.

What git information does the handoff capture?▼

It captures the current commit hash via git rev-parse HEAD, the branch name via git branch --show-current, and the repository URL via git remote get-url origin, recording them in the document frontmatter.