handoff

Solid

Use when a coding session is getting long, before stopping complex implementation/migration/debugging work, when the operator says "prepare a handoff" / "hand this off" / "continue in a new chat" / "/handoff", or when a long autonomous run needs continuity (Mode run-ledger, announced in chat) — archives the superseded restart state to docs/tmp/handoff/archive/ (paper trail), then writes the active state to docs/tmp/handoff.md so a fresh AI session resumes from the exact current point without the previous chat. Do NOT use for routine commits, human-facing status reports, formal implement/deploy role relays (those are docs/tmp/handoff/<date>-<slug>-{implement,deploy}.md), or when no meaningful code/test/schema/config/decision change happened this session.

AI & Automation 9 stars 0 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%
33
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Handoff > **Style:** Mode-B-lite. Produces the active-continuity artifact `docs/tmp/handoff.md` (FR-23 Tier 2) for the NEXT AI coding agent — not a human PM report. Operator-triggered (`invocation: manual`) for **restart** mode; **`Mode: run-ledger`** is the sole sanctioned autonomous write (long-run continuity, announced in chat). ## Purpose Capture the exact current state of a coding session into `docs/tmp/handoff.md` so a brand-new AI session continues without the previous chat. Long sessions degrade and compaction is lossy; a structured handoff preserves goal, repo state, decisions, in-flight files, failed attempts, constraints, and the single next action. This is the **active** restart state; formal role-relay prompts (implement/deploy/architect) are separate dated files under `docs/tmp/handoff/` produced by `implementation-planning` / `release-deploy-reporting`. **Two modes** (header `Mode:` line; absent in a legacy file → treat as restart): **restart** — operator-triggered snapshot for the next session; **run-ledger** — a long autonomous run's continuity note, written without operator trigger and announced in chat (one line), so context death mid-run loses nothing. A fresh session reading `Mode: run-ledger` resumes from records (read the ledger + cited artifacts first, resume from the last durable fact — `task-delegation` successor contract); a run-ledger is a continuity note, not a role-relay draft (it does not breach "AI Developer acknowledges; doesn't draft")....

Details

Author
fusebase-dev
Repository
fusebase-dev/fusebase-flow
Created
4 months ago
Last Updated
1 weeks ago
Language
Shell
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category