APromptAura
0

Handoff protocol between specialized agents with no context loss

auto-checked, 23 hours old
AauraNovice

The prompt

0 copies
Design a handoff protocol for when one specialized agent (agent_a_role) needs to pass a task to another (agent_b_role) mid-conversation. Requirements: 1. What exactly gets handed off: define the minimum sufficient package (not the full conversation dump) so agent B can pick up correctly, including what agent A already tried/ruled out so agent B doesn't repeat wasted work. 2. The trigger condition for handoff: specific signals that this is now outside agent A's competence (not a vague 'if it seems hard'), tailored to what agent A vs agent B are each actually good at. 3. What agent B is required to acknowledge before proceeding: confirm it understood the handed-off context correctly, in a form the user can also see, so a miscommunication is caught before agent B acts on a misunderstanding. 4. How the user experiences this: should the handoff be visible/announced to the user or seamless, and why, given the stakes of this specific handoff. 5. What happens if agent B determines the handoff was wrong (task actually still belongs with agent A, or belongs with a third agent) - avoid a ping-pong loop. Agent A role: agent_a_role Agent B role: agent_b_role Domain: domain

Run it in your model, then come back and report whether it worked, including the model and version.

Where it has been run

People and our automated sweep are counted separately. Only the People column is someone vouching for this prompt.

ModelVersionPeopleBrokeAutoLast
ClaudeHaiku 4.5001/123 hours ago

Example output

Agent A: general support triage. Agent B: billing disputes specialist. Handoff package: the customer's original complaint verbatim, agent A's classification reasoning ('flagged as billing dispute because customer disputes a specific charge amount'), and what agent A already checked (confirmed account is active, confirmed no open disputes already on file) so agent B doesn't redo those checks. Trigger: specifically when the customer disputes a charge amount or timing, not just any billing question (a 'when does my subscription renew' question stays with agent A, that's not a dispute). Agent B acknowledgment, shown to the user: 'Picking this up: you're disputing a $49 charge from March 3rd that you don't recognize. Let me pull the transaction details.' This surfaces any misclassification immediately, if the customer says 'no, I recognize the charge, I just think it's the wrong amount', that's caught before agent B proceeds on the wrong premise. User visibility: handoff is announced, not seamless, because billing disputes often need a paper trail the customer should be aware exists. Wrong-handoff recovery: if agent B determines this isn't actually a dispute, it hands back to agent A with its own reasoning, capped at one bounce, a second miscategorization escalates to a human rather than bouncing again.

0 comments

Sign in to comment or report what this prompt did for you.

Sign in

No comments yet. Run the prompt and report what you got.