handoff

Capture session context and append a structured handoff to handoff.md.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/kpeez/agentspec --skill handoff-kpeez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/kpeez/agentspec/tree/main/skills/handoff
Command: npx skills add https://github.com/kpeez/agentspec --skill handoff-kpeez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture session context before ending to ensure a seamless resume by the next agent. Use when ending a session, switching contexts, or when the user runs /handoff.

Core Features & Use Cases

  • Identify the active feature: If an argument is provided, use that feature; otherwise, consult specs for the most recently modified ledger.md and, if none exist, summarize the session.
  • Gather session context: Document what was accomplished, what is in progress or blocked, files touched, and any non-obvious context discovered.
  • Update ledger.md: Move completed items to Done; refresh Next; add new context; adjust Phase and Blocked status.
  • Write handoff summary: Append to specs/<feature>/handoff.md with a structured session report including Completed, In Progress, Blocked, Critical Context, Files Touched, and Resume Command.
  • Confirm the handoff is complete and ledger.md reflects the latest state.

Quick Start

Summarize the current session and append a new handoff.md under specs/<feature>/handoff.md detailing completed work, in-progress items, blockers, and critical context.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I capture AI agent session context for seamless handoffs?

Capture session context by identifying the active feature, documenting completed work, in-progress items, blockers, and critical context, then appending a structured handoff summary to specs/<feature>/handoff.md.

What is the best way to preserve context when switching AI agent sessions?

Preserve context by updating the relevant spec ledger.md to move completed items to Done and appending a structured session report with files touched and a resume command to handoff.md.

How do I track in-progress work and blockers before ending an AI coding session?

Track in-progress work and blockers by running a handoff process that identifies the most recently modified spec ledger, documents current session state, and writes a structured summary to handoff.md.

Does the handoff skill require existing spec files to function?

No, it does not require existing spec files. If a feature argument is provided it uses that feature; otherwise it consults specs for the most recently modified ledger.md, and if none exist it summarizes the session.

Can I specify which feature to capture context for during a session handoff?

Yes, you can specify a feature by providing it as an argument. If no argument is provided, the skill automatically consults specs for the most recently modified ledger.md to determine the active feature.

What limitations exist when summarizing session context without a spec ledger?

Without a spec ledger, the skill summarizes the session directly instead of moving completed items to Done or refreshing the Next section, meaning the structured ledger update is bypassed for the handoff.