Agentic Design

Patterns
๐Ÿ‘จโ€๐Ÿ’ผ

Supervisor-Worker Pattern(SVW)

Orchestrator-worker architecture where a lead agent coordinates specialized subagents for parallel task execution

Complexity: highMulti-Agent

๐ŸŽฏ 30-Second Overview

Pattern: Orchestrator-worker architecture where a lead agent coordinates specialized subagents for parallel task execution

Why: Achieves 90% performance improvement through parallel exploration and specialized expertise while maintaining centralized quality control

Key Insight: Dynamic task decomposition + separate worker contexts + real-time coordination = superior research quality at 15x token cost

โšก Quick Implementation

1Decompose:Break query into 3-5 parallel subtasks
2Spawn:Create specialized worker agents dynamically
3Coordinate:Monitor progress across separate contexts
4Adapt:Spawn additional workers if needed
5Synthesize:Aggregate all findings into final result
Example: query โ†’ decompose(4_tasks) โ†’ spawn_workers() โ†’ monitor_parallel() โ†’ synthesize_results()

๐Ÿ“‹ Do's & Don'ts

โœ…Use separate context windows for each worker agent
โœ…Implement dynamic worker spawning based on complexity
โœ…Monitor worker progress and adjust strategies in real-time
โœ…Set clear objectives and success criteria for each worker
โœ…Use interleaved thinking for worker self-evaluation
โœ…Implement timeout and failure handling for workers
โœ…Cache expensive operations and intermediate results
โœ…Use structured output formats for worker communication
โŒCreate too many workers (diminishing returns after 5-7)
โŒShare context between workers (reduces parallel benefits)
โŒIgnore token consumption explosion (15x normal usage)
โŒSkip quality control in final synthesis step
โŒUse for simple queries that don't need decomposition
โŒForget to implement worker error propagation handling

๐Ÿšฆ When to Use

Use When

  • โ€ข Complex, multi-domain research queries
  • โ€ข Open-ended analysis requiring multiple perspectives
  • โ€ข Tasks benefiting from parallel exploration
  • โ€ข Research-intensive workflows
  • โ€ข High-accuracy requirements worth extra cost
  • โ€ข Problems requiring diverse expertise areas

Avoid When

  • โ€ข Simple, single-domain questions
  • โ€ข Cost-sensitive applications (15x token usage)
  • โ€ข Real-time/low-latency requirements
  • โ€ข Well-defined procedural tasks
  • โ€ข Limited API quota scenarios
  • โ€ข Sequential dependency workflows

๐Ÿ“Š Key Metrics

Research Quality
90% improvement over single-agent
Token Consumption
15x baseline usage (cost planning)
Parallel Efficiency
% workers completing successfully
Task Decomposition
Optimal subtask count (3-5 workers)
Synthesis Quality
Coherence of final aggregated result
Worker Utilization
% workers contributing unique value
Error Recovery
% failed workers handled gracefully

๐Ÿ’ก Top Use Cases

Research Analysis: "Impact of AI on healthcare" โ†’ Medical, Regulatory, Economic, Ethics workers โ†’ Comprehensive report
Market Intelligence: "Competitor analysis" โ†’ Product, Financial, Strategy, Technology workers โ†’ Strategic insights
Scientific Literature: "Climate change solutions" โ†’ Physics, Policy, Engineering, Economics workers โ†’ Multi-disciplinary review
Investment Due Diligence: "Company evaluation" โ†’ Financial, Market, Risk, Technical workers โ†’ Investment recommendation
Policy Research: "Education reform" โ†’ Academic, Economic, Social, Implementation workers โ†’ Policy framework
Technology Assessment: "Blockchain adoption" โ†’ Technical, Business, Legal, Social workers โ†’ Adoption strategy
Crisis Analysis: "Supply chain disruption" โ†’ Logistics, Economic, Geopolitical, Risk workers โ†’ Response plan
Product Strategy: "Market entry analysis" โ†’ Customer, Competitive, Regulatory, Technical workers โ†’ Go-to-market plan

References & Further Reading

Deepen your understanding with these curated resources

Contribute to this collection

Know a great resource? Submit a pull request to add it.

Contribute

Patterns

closed

Loading...