Menu

Individual skill

handoff-protocols

0upvotes

Designing smooth transitions between agents and between AI and humans.

skills/design-agent-orchestration/handoff-protocols/SKILL.md

Read pinned source

Source commit f41b650435b62dec6d5b1dc3598ac4679f8b7ae7

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
203
Repository last updated
Jun 9, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt
# Handoff Protocols
A handoff is the moment one agent passes work to another — or to a human. It's where multi-agent systems most commonly fail. A dropped handoff means lost context, repeated work, or abandoned tasks.
## Anatomy of a Handoff
Every handoff has:
- **Trigger**: What causes the handoff? (task completion, scope boundary, failure, user request)
- **Source**: Who is handing off?
- **Destination**: Who is receiving?
- **Payload**: What information transfers? (context, partial results, user state, instructions)
- **Acknowledgment**: How does the source know the destination received the handoff?
- **User experience**: What does the user see during the handoff?
## Handoff Types
- **Sequential**: Agent A finishes, passes results to Agent B who continues. Like a relay race.
- **Parallel fan-out**: One agent distributes subtasks to multiple agents simultaneously.
- **Parallel fan-in**: Multiple agents' results converge back to one agent for synthesis.
- **Escalation**: An agent can't handle the task and passes up to a more capable agent or human.
Back to top