Web
AuraScore 85/100

Multi-Agent Web Task Decomposition and Routing Framework

Design deterministic DAGs, state handoffs, and fallback loops for chained autonomous browser and API agents.

Use this template when building complex multi-agent workflows across web services. It establishes clear agent boundaries, shared state contracts, and human-in-the-loop intervention gates.

Template

Role: Lead Agentic Systems Engineer specializing in deterministic multi-agent state machines and distributed web execution graphs.

Context

  • Orchestration Architecture Model: {{orchestration_model}}
  • Workflow Trigger Events: {{workflow_trigger_events}}
  • Specialized Agent Fleet: {{agent_specializations}}
  • Persistent State Store: {{state_store_backend}}
  • Human-in-the-Loop Verification Gates: {{human_in_the_loop_gates}}
  • Failure Recovery Protocol: {{failure_recovery_protocol}}

Task

Synthesize a deterministic multi-agent workflow routing framework that orchestrates specialized web agents across complex task graphs, maintaining synchronized session state and strict execution boundaries.

Method

  1. Deconstruct incoming tasks triggered by {{workflow_trigger_events}} into directed acyclic graph (DAG) sub-tasks.
  2. Map specific sub-task nodes to designated domain agents within {{agent_specializations}}.
  3. Define the inter-agent handoff schema and state serialization protocols backed by {{state_store_backend}}.
  4. Configure decision boundaries for the central controller using {{orchestration_model}} to govern state transitions.
  5. Establish dynamic evaluation gates that enforce {{human_in_the_loop_gates}} for high-stakes actions or irreversible state changes.
  6. Construct fallback loops and circular dependency breakers governed by {{failure_recovery_protocol}}.
  7. Formulate context pruning routines that strip redundant conversational history before routing state to subsequent agents.
  8. Define final state aggregation and user-facing result compilation stages.

Constraints

  • MUST define deterministic state-machine transitions with zero infinite-loop potential.
  • MUST NOT allow downstream agents direct mutation rights to upstream state nodes without controller approval.
  • Every agent handoff payload must contain an idempotency key and trace ID.
  • Context window allocation per handoff must not exceed predefined token caps.

Output format

  1. Orchestration Topology and Task DAG Breakdown
  2. Inter-Agent Communication and Handoff Schema
  3. State Persistence and Hydration Specification
  4. Human-in-the-Loop Interception Protocol
  5. Failure Triage and Recovery Decision Tree

Self-review

  • Check that all nodes in the DAG have defined terminal states and fallback routes.
  • Ensure state persistence methods under {{state_store_backend}} handle concurrent agent access safely.
  • Verify human review criteria are explicit with defined timeout thresholds.
AuraScore breakdown
85/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency7/10 · Adequate

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness5/5 · Strong

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

developers
developers-web
autonomous-agents-workflows
multi-agent
orchestration
workflow-chains