/handoff

> Transfer context between agents or sessions with structured state preservation.

170 stars

byMiosa-osa

View on GitHub Installation ↓

Best use case

/handoff is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

> Transfer context between agents or sessions with structured state preservation.

Teams using /handoff should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/handoff/SKILL.md --create-dirs "https://raw.githubusercontent.com/Miosa-osa/canopy/main/library/skills/workflow/handoff/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/handoff/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How /handoff Compares

Feature / Agent	/handoff	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

> Transfer context between agents or sessions with structured state preservation.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# /handoff

> Transfer context between agents or sessions with structured state preservation.

## Usage
```
/handoff --to <agent|session> [--context "<summary>"] [--files "<file-list>"]
```

## What It Does
Packages the current working context into a structured handoff document that another agent or session can load to continue work without losing state. Captures: current progress, open decisions, blocking issues, relevant files, and next steps.

## Implementation
1. **Capture state** -- current task, progress, decisions made, files modified.
2. **Package context** -- write structured handoff document:
   - What was done
   - What's in progress
   - What's blocked
   - Key decisions made (with rationale)
   - Files to read
   - Next steps
3. **Write handoff** -- save to `work/handoff-<timestamp>.md`.
4. **Notify** -- if handing to a specific agent, include routing metadata.

## Examples
```bash
# Hand off to another agent
/handoff --to "backend-go" --context "Auth flow designed, need implementation"

# Hand off between sessions
/handoff --to session --files "lib/auth.ex, test/auth_test.exs"

# Quick handoff with inline context
/handoff --to "test-automator" --context "Feature implemented, needs test coverage"
```

## Command