Loading patterns…

👥

Role-Based Teamwork

Structured agent teams with defined roles and responsibilities

Complexity: mediumWorkflow Orchestration

In 30 seconds

What: Assigns distinct roles to agents with specific capabilities and responsibilities, coordinating their work through defined handoffs and delegation patterns.
When to use: Complex projects requiring specialized expertise where different agents need clear ownership and sequential or parallel task execution.
Watch out: Role boundaries become rigid bottlenecks; agents block waiting for role-holders instead of adapting when someone is unavailable or overloaded.

Ask the AI expert about this pattern

Opens the assistant with your question prefilled. You review it before sending.

Get this catalog as an MCP server Tune a prompt for this pattern

Structured agent teams with defined roles and responsibilities

Clear role definitions
Hierarchical team structures
Task delegation patterns
Role-specific capabilities
Team coordination protocols
Performance accountability

The Agent Architect

One pattern, one tradeoff, one production failure story. A short weekly briefing for people building agentic systems.

Weekly email, one-click unsubscribe. We only use your address to send the briefing.

References

The papers, specifications, and repositories this pattern is based on.

AutoGen: Enabling Next-Gen LLM Applications via Multi-Agent Conversation (2023)arXiv:2308.08155
AgentScope: Flexible Multi‑Agent Platform (2024)

From the engineer behind this catalog

Get your agent architecture reviewed

This page documents one pattern. Your system runs dozens, and most failures live in how they fit together. Have the whole design reviewed against the 288 patterns in this catalog: architecture, reliability, evaluation and cost, every finding mapped to the pattern that fixes it.

€750 instead of €1,500, one week, written report and walkthrough call, until 30 September

See the review

Patterns

Loading patterns…

Design Patterns & Techniques

Loading patterns…

👥

Role-Based Teamwork

Structured agent teams with defined roles and responsibilities

Complexity: mediumWorkflow Orchestration

In 30 seconds

What: Assigns distinct roles to agents with specific capabilities and responsibilities, coordinating their work through defined handoffs and delegation patterns.
When to use: Complex projects requiring specialized expertise where different agents need clear ownership and sequential or parallel task execution.
Watch out: Role boundaries become rigid bottlenecks; agents block waiting for role-holders instead of adapting when someone is unavailable or overloaded.

Ask the AI expert about this pattern

Opens the assistant with your question prefilled. You review it before sending.

Get this catalog as an MCP server Tune a prompt for this pattern

Core Mechanism

Structured multi-agent collaboration where each agent is assigned a clear role (e.g., supervisor, planner, researcher, implementer, reviewer, verifier/judge, tool specialist) with defined responsibilities, capabilities, and permissions. Roles coordinate via typed messages and artifact handoffs, enabling division of labor, accountability, and repeatable workflows. Common implementations use supervisor–worker or scheduler patterns with least‑privilege credentials and auditable handoffs.

Workflow / Steps

Define role catalog: supervisor, planner, researcher, implementer, reviewer, verifier/judge, tool ops.
Instantiate team: bind prompts, tools, credentials, SLAs, and budgets to each role.
Intake and triage: normalize goal, constraints, risk, and evaluation rubric.
Plan and assign: planner decomposes tasks; supervisor assigns to roles with acceptance criteria.
Execute loops: roles act with tools/retrieval; produce structured artifacts and traces.
Handoffs: reviewer/verifier validate outputs; resolve conflicts or request revisions.
Escalation: supervisor routes exceptions; optional human‑in‑the‑loop for high‑risk steps.
Synthesize and deliver: compile final output with provenance and metrics.
Learn and update: refine role prompts, policies, and routing from outcomes.

Best Practices

Create explicit role cards (purpose, inputs/outputs, tools, guardrails, success criteria).

Use capability/permission scopes and short‑lived credentials per role (least privilege).

Standardize handoff schemas (task, artifact refs, confidence, costs, next actions).

Bound loops and depth; cap per‑role tokens, time, and retries to avoid ping‑pong.

Summarize across handoffs; store large artifacts externally and pass references.

Prefer small models for routing/checks; reserve larger models for hard reasoning roles.

Instrument per‑role metrics: utilization, handoff acceptance, rework, cost, and latency.

Add human review gates for safety‑critical or high‑impact decisions.

When NOT to Use

Simple, single‑step tasks where a single agent meets quality and SLOs.
Strict real‑time paths where additional handoffs break latency budgets.
Poorly specified goals where role boundaries and acceptance criteria cannot be defined.
Highly coupled tasks requiring continuous shared context best handled by one agent.

Common Pitfalls

Unbounded role ping‑pong and re‑review cycles causing token/cost blowups.
Ambiguous ownership; unclear acceptance criteria for role outputs.
Permission sprawl or long‑lived tokens beyond role scope.
Context drift and stale memory across roles without summarization.

Key Features

Explicit role definitions with scopes and policies

Supervisor/scheduler for assignment and escalation

Typed messages and artifact‑centric handoffs

Per‑role budgets, SLAs, and utilization tracking

Guardrails and approvals on sensitive actions

Observability: traces, costs, provenance, and audits

KPIs / Success Metrics

End‑to‑end task success; per‑role handoff acceptance and first‑pass yield.
Rework rate; escalation rate; MTTR with/without human assist.
Tokens/time/cost per successful task and per role; utilization by role.
Verifier/judge agreement and policy compliance rates.

Token / Resource Usage

Set per‑role token/time budgets and stop criteria; summarize on each handoff.
Use small models for routing/checks; cache retrievals and artifacts for reuse.
Cap concurrency and retries per role; stream partials and early‑exit on confidence.
Store large artifacts externally; pass compact references and provenance.

Best Use Cases

Software development lifecycle: planner → coder → reviewer → tester → deploy.
Research and content production: researcher → writer → editor → fact‑checker.
Customer support and triage: classifier → specialist → quality verifier.
Due diligence and audits: evidence gathering → analysis → verification → report.

References & Further Reading

Academic Papers

Implementation Guides

Tools & Libraries

Community & Discussions

Structured agent teams with defined roles and responsibilities

Clear role definitions
Hierarchical team structures
Task delegation patterns
Role-specific capabilities
Team coordination protocols
Performance accountability

The Agent Architect

One pattern, one tradeoff, one production failure story. A short weekly briefing for people building agentic systems.

Weekly email, one-click unsubscribe. We only use your address to send the briefing.

References

The papers, specifications, and repositories this pattern is based on.

AutoGen: Enabling Next-Gen LLM Applications via Multi-Agent Conversation (2023)arXiv:2308.08155
AgentScope: Flexible Multi‑Agent Platform (2024)

From the engineer behind this catalog

Get your agent architecture reviewed

€750 instead of €1,500, one week, written report and walkthrough call, until 30 September

See the review

Loading patterns…

Role-Based Teamwork

In 30 seconds

Ask the AI expert about this pattern