flow-handoff

Create a context handoff document with current task and Git history.

15|4|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/cofin/flow --skill flow-handoff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flow-handoff
Source: https://github.com/cofin/flow/tree/main/templates/codex/skills/flow-handoff
Command: npx skills add https://github.com/cofin/flow --skill flow-handoff

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enables the seamless transfer of AI development sessions by creating a comprehensive context handoff document, preventing loss of work and context.

Core Features & Use Cases

  • Session State Capture: Gathers current flow, task, and recent Git activity.
  • Handoff Document Generation: Creates a structured .agent/handoff.md file detailing progress, decisions, and next steps.
  • Beads Integration: Updates Beads with a summary of the handoff for persistent memory.
  • Use Case: If you need to stop working on a complex AI-driven coding task and resume it later or on a different machine, this Skill ensures all necessary context is saved.

Quick Start

Run the flow-handoff skill to create a session context handoff document.

Frequently Asked Questions about flow-handoff

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

FAQPage Schema
How do I save an AI development session to resume it later?

To save an AI development session, generate a context handoff document that captures your active flow, current task details, and recent Git log history. This compiles progress and next steps into a structured file for seamless session transfer.

Why does my AI coding assistant lose context when I switch machines?

Your AI coding assistant loses context because session state is not automatically persisted. Creating a context handoff document with active flow, task details, and Git history ensures the necessary context is saved and ready for resumption on a different machine.

Can I sync my AI session context with Beads for persistent memory?

Yes, you can sync your AI session context with Beads. The session transfer process updates Beads with a summary of the handoff, ensuring persistent memory of your progress, decisions, and next steps across development sessions.

What is the best way to transfer an AI development session between environments?

The best way to transfer an AI development session is to generate a structured handoff document. This document compiles your current task details from Beads and recent Git log history, providing clear next steps and context for resumption.

Do I need Git to create a context handoff document for my AI session?

Git is used to capture recent log history for the context handoff document. While the session transfer process compiles active flow and task details from Beads, Git history provides the necessary code activity context for accurate resumption.