Multi-Agent Handoff Specification
Writes a precise handoff contract between two agents: what gets passed, in what format, and what the receiving agent assumes.
When to use this
Use when two agents (or an agent and a human) need a clean boundary, to avoid silently dropped context or mismatched assumptions.
Prompt template
You are designing a handoff between two agents.
Agent A ({{agent_a_role}}) hands off to Agent B ({{agent_b_role}}).
Reason for handoff: {{handoff_trigger}}
Specify:
1. The exact payload Agent A must pass (fields, types, required vs. optional).
2. What Agent B is allowed to assume is already true when it receives the handoff.
3. What Agent B must NOT assume, and must re-check itself.
4. What happens if Agent B cannot proceed (hands back? escalates to a human? retries?).
5. A one-paragraph example handoff payload for this scenario.Customize
Agent A's role is required
Agent B's role is required
Reason for handoff is required
Preview
You are designing a handoff between two agents.
Agent A ({{agent_a_role}} missing) hands off to Agent B ({{agent_b_role}} missing).
Reason for handoff: {{handoff_trigger}} missing
Specify:
1. The exact payload Agent A must pass (fields, types, required vs. optional).
2. What Agent B is allowed to assume is already true when it receives the handoff.
3. What Agent B must NOT assume, and must re-check itself.
4. What happens if Agent B cannot proceed (hands back? escalates to a human? retries?).
5. A one-paragraph example handoff payload for this scenario.Usage instructions
Name the two agents by role (not implementation detail) and the specific condition that triggers the handoff; be concrete about the trigger so the contract is testable.
Example output
A payload spec (ticket id, customer id, classification confidence, raw message, required; proposed resolution, optional), an assumption list (classification is correct enough to route, but NOT that the amount is correct), and an escalation rule (hand back to a human if confidence < 0.6).
Limitations
This defines a contract, not a serialization format; you'll still need to translate it into your framework's actual message schema.
Rate this prompt
Not yet rated