Multi-Agent Orchestration Protocol and Handoff Brief

Role: Principal Autonomous Systems Workflow Engineer specializing in multi-agent routing topologies and deterministic state machines.

Context

• Orchestrator Engine: {{orchestration_engine}}
• Primary Initiator Agent: {{primary_agent_role}}
• Downstream Agent Cluster: {{downstream_agent_cluster}}
• Shared Memory State Model: {{shared_memory_state}}
• Handoff Trigger Conditions: {{handoff_trigger_events}}
• Fallback & Escalation Route: {{fallback_strategy}}

Task

Author a comprehensive multi-agent handoff brief that establishes strict communication contracts, state synchronization schemas, and termination criteria across the agent topology.

Method

1. Deconstruct the operational scope of {{primary_agent_role}} and its delegation interfaces with {{downstream_agent_cluster}}.
2. Specify the payload contract that must be validated prior to emitting handoff tokens in {{orchestration_engine}}.
3. Map every condition in {{handoff_trigger_events}} to a discrete state transition and routing destination.
4. Design state preservation protocols that serialize {{shared_memory_state}} without loss or bloat.
5. Establish cycle-detection mechanisms to prevent recursive looping between cooperating agents.
6. Detail human-in-the-loop triggers and automated graceful degradation paths defined by {{fallback_strategy}}.
7. Outline concurrency handling when multiple downstream nodes evaluate sub-tasks simultaneously.
8. Produce a chronological trace walkthrough illustrating an end-to-end task execution from ingress to terminal state.

Constraints

• MUST define explicit schema keys for context transfer within {{shared_memory_state}}.
• MUST NOT permit ambiguous handoff criteria that allow simultaneous uncontrolled multi-node execution.
• MUST include maximum step ceilings to prevent unbounded execution cycles.
• Keep terminology strictly aligned with standard distributed systems and agent orchestration concepts.
• Structure must remain between 900 and 1,300 words.

Output format

Deliver a technical orchestration brief structured as:

1. Topology Blueprint & Agent Role Definitions
2. Handoff Contract Specifications (Trigger, Payload Schema, Validation Rules)
3. Shared State Persistence Protocol (Read/Write Rules, Pruning Policies)
4. Cycle Prevention and Timeout Controls
5. Human Escalation & Fallback Procedures
6. End-to-End Sequence Walkthrough

Self-review

• Does every handoff trigger map cleanly to a single recipient or deterministic routing node?
• Is {{shared_memory_state}} protected against write-conflicts during multi-agent handoffs?
• Are failure thresholds and human escalation paths completely explicit?