handoff

Generate structured handoff documents and store them to shared-context.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/Skobyn/g.c.l.a.w --skill handoff-skobyn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/Skobyn/g.c.l.a.w/tree/main/skills/handoff
Command: npx skills add https://github.com/Skobyn/g.c.l.a.w --skill handoff-skobyn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pass context between agents or sessions by generating structured handoffs that preserve task state for seamless continuation or archiving.

Core Features & Use Cases

  • Writes to a shared-context so the next agent or session can resume without re-discovery.
  • Optionally stores a one-line summary in the Memory Bank for quick recall.

Quick Start

Generate a handoff document that captures the current task context and saves it to the shared-context.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I pass context between agents when switching tasks mid-workflow?

Pass context between agents by generating structured handoff documents that preserve task state. These documents are stored to a shared-context, allowing the next agent or session to resume work without re-discovery of previous progress.

What is the best way to preserve task state for resuming work in a new session?

The best way to preserve task state is creating a structured handoff that captures current context. The handoff is written to shared-context for seamless continuation, with an optional one-line summary saved to the Memory Bank for quick recall.

When do I need to generate a handoff document for my workflow?

Generate a handoff document when switching work between manager agents mid-task, resuming work in a new session, or archiving the state of a long-running project to ensure no context is lost during transitions.

Can I store a summary of my agent handoff in the Memory Bank?

Yes, you can optionally store a one-line summary in the Memory Bank alongside the full structured handoff. This provides quick recall of the task state while the complete context remains available in the shared-context.

Does generating structured handoffs require any dependencies?

Generating structured handoffs requires no external dependencies. The skill operates independently to capture task context, writing directly to shared-context via context_write and optionally saving a summary to the Memory Bank.