handoff

Generate structured HANDOFF.md notes capturing coding work status, progress, and next steps.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When pausing, transferring, or resuming coding work after interruptions like context loss, token limits, machine restarts, or session changes, critical context about goals, progress, blockers, and next steps is often lost, leading to wasted time re-discovering work state and re-running completed steps.

Core Features & Use Cases

  • Structured Handoff Notes: Generates standardized, skimmable handoff documents with clear sections for goals, workflow stage, completed work, in-progress tasks, next steps, artifacts, and risks.
  • Smart File Handling: Automatically selects user-accessible save locations, updates existing HANDOFF.md files in place, and avoids overwriting unrelated handoff notes by prompting for confirmation or creating dated adjacent files.
  • Use Case: If you are mid-debugging a critical production bug and hit a token limit mid-investigation, use this skill to generate a complete handoff note so the next coding agent can pick up exactly where you left off without re-running prior diagnostic steps.

Quick Start

Use the handoff skill to capture a restart-safe handoff note for your current unfinished coding work and save it to a reachable HANDOFF.md file in your active workspace.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I preserve coding agent context when hitting a token limit?

To preserve coding agent context when hitting a token limit, generate a structured handoff note capturing goals, progress, and blockers. This ensures the next agent can resume work immediately without re-running prior diagnostic steps.

What is the best way to transfer unfinished coding work to another agent?

Transferring unfinished coding work to another agent requires a standardized handoff document detailing completed work and next steps. This enables fast, error-free work restarts with full visibility into the current workflow stage.

How do I resume a debugging session after a machine restart without losing progress?

Resuming a debugging session after a machine restart involves saving a structured handoff note to a HANDOFF.md file. This captures in-progress tasks and risks, preventing the loss of critical context during the session change.

Can I update an existing HANDOFF.md file in place without overwriting unrelated notes?

Yes, you can update an existing HANDOFF.md file in place. The system avoids overwriting unrelated handoff notes by prompting for confirmation or automatically creating a dated adjacent file for the new context.

What sections should be included in agent handoff notes for work resumption?

Agent handoff notes for work resumption should include dedicated sections for status, goals, completed work, in-progress tasks, artifacts, and risks. This structured format enables fast skimming and error-free work restarts.

Does this context preservation approach work for all coding workflows requiring agent handoffs?

Yes, this context preservation approach applies to all coding workflows requiring handoff of unfinished work to other agents or team members. It handles interruptions including context loss, token pressure, and session changes.