| name | handoff-protocol |
| model | sonnet |
| description | Produces a structured handoff package (markdown document) containing objective, required context file list, task definition, definition of done, constraints, and next steps for the receiving agent. Use when: 'hand off to the next agent', 'prepare this for handoff', 'is this handoff package complete', 'ensure nothing is lost in the transition'. |
| category | agent-orchestration |
| triggers | ["hand off to the next agent","prepare this for handoff","is this handoff package complete","ensure nothing is lost in the transition"] |
| tier | 1 |
| agents | ["primary"] |
| tool_dependencies | ["file_system"] |
| inputs | [{"name":"objective","type":"string","description":"The objective being handed off to the receiving agent","required":true},{"name":"context_files","type":"string[]","description":"List of context file paths the receiving agent needs","required":false}] |
| outputs | [{"name":"handoff_package","type":"string","description":"Structured handoff markdown document with objective, context files, task definition, definition of done, and constraints"}] |
Agent Handoff Protocol Skill
Version: 1.0
Created: 2026-02-04
Author: Manus AI
Purpose: To provide a clear, repeatable protocol for handing off work between agents (e.g., Manus to implementation agents, Manus to Cipher), ensuring no loss of context and a high probability of success.
I. The Philosophy: The Sacred Relay
In a multi-agent ecosystem, a handoff is a sacred relay. It is the moment where one agent passes the baton of responsibility to another. A fumbled handoff leads to dropped context, wasted effort, and a broken workflow. A clean handoff is a moment of trust and shared understanding, where the receiving agent is not just given a task, but is fully equipped to carry it forward.
This protocol transforms the handoff from a hopeful transfer into a rigorous, verifiable exchange. It is an act of respect for the receiving agent, acknowledging that their ability to succeed is entirely dependent on the quality of the context they are given.
II. When to Use This Skill
- Always use this skill when one agent's work is complete and another agent must begin the next phase.
- Manus → Implementation Agent: When a specification is complete and ready for implementation.
- Manus → Cipher: When research is complete and a creative or divergent perspective is needed.
- Any Agent → Any Agent: Whenever responsibility for a task is transferred.
III. The Handoff Workflow
Step 1: Prepare the Handoff Package
The sending agent is responsible for preparing a complete and self-contained "handoff package." This is a markdown document that contains everything the receiving agent needs to know. Use the template from Section IV.
Step 2: Verify the Package with the Checklist
Before initiating the handoff, the sending agent must verify the package against the Handoff Checklist in Section V. This is a self-assessment to ensure quality.
Step 3: Initiate the Handoff
The sending agent initiates the handoff by creating a task for the receiving agent, with the handoff package as the primary input.
Example Handoff Task:
- Agent: Implementation Agent (Zenflow, Claude Code, etc.)
- Task: Implement the v0.0.26 Breadcrumb feature.
- Input:
handoffs/v0.0.26/01_breadcrumb_handoff.md
Step 4: The Receiving Agent's Acceptance
The receiving agent's first action is to read the handoff package and confirm that it has everything it needs to proceed. If the package is incomplete, the receiving agent must immediately return the task to the sender with a request for more information.
