handoff

Generate a standardized 16-section handoff document capturing coding session state.

6|Updated May 29, 2026
One-click install
npx skills add https://github.com/fusebase-dev/fusebase-flow --skill handoff-fusebase-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/fusebase-dev/fusebase-flow/tree/main/flow-skills/handoff
Command: npx skills add https://github.com/fusebase-dev/fusebase-flow --skill handoff-fusebase-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Long AI coding sessions lose critical context when restarted, leading to repeated explanation of prior work, lost progress on complex implementation, migration, or debugging tasks, and broken continuity for autonomous long-running workflows.

Core Features & Use Cases

  • Structured Session Capture: Generates a standardized 16-section handoff document that records the exact current state of the coding session, including goals, repo status, key decisions, in-flight changes, failed attempts, and the single next executable action.
  • Dual Mode Support: Supports operator-triggered manual restart handoffs for paused work, and autonomous run-ledger mode for long-running tasks to preserve continuity if context is lost mid-execution.
  • Use Case: If you are mid-debugging a complex production issue and need to pause your session, use this skill to create a handoff so the next AI session can resume work immediately without re-establishing context.

Quick Start

Use the handoff skill when you need to pause a long coding session and preserve all current progress, decisions, and next steps for the next AI session to continue seamlessly.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I preserve AI coding session context across restarts?

To preserve AI coding session context across restarts, you can generate a standardized machine-readable handoff artifact. This document captures repo status, key decisions, in-flight changes, and the next executable action for seamless resumption.

What is the best way to resume a complex debugging task after an AI session drops?

The best way to resume a complex debugging task after an AI session drops is using a session continuity handoff. It records failed attempts and the exact next step so the new AI session can continue immediately without re-establishing context.

Can I maintain continuity for autonomous long-running coding workflows?

Yes, you can maintain continuity for autonomous long-running coding workflows using a run-ledger mode. This mode continuously preserves execution state so progress is not lost if context is unexpectedly dropped mid-execution.

How does a structured handoff document help with code migration workflows?

A structured handoff document helps with code migration workflows by recording the exact session state, including goals, repo status, and in-flight work. This eliminates repeated context explanation when manually pausing and restarting migration tasks.

What specific details are captured when preserving coding progress for an AI handoff?

Preserving coding progress for an AI handoff captures details across 16 sections, including goals, repo status, key decisions, failed attempts, and the single next executable action needed to seamlessly resume the development workflow.

When should I trigger a manual session restart handoff?

You should trigger a manual session restart handoff when you need to pause a long coding session mid-task. This generates a standardized artifact ensuring the next AI session can resume work immediately without lost progress.