Flows are lightweight orchestrators that package common coordination patterns.

Why flows?

• Make patterns reusable across teams
• Reduce “glue code”
• Provide sensible defaults for reliability

Examples of patterns

• Parallel: run agents/tasks concurrently
• Router: choose the next hop dynamically
• Round-robin / Selector: iterate across a set of agents
• Critic review: draft → critique → revise loops
• Map-reduce: fan-out work, aggregate results
• P2P / Auction: negotiation and allocation patterns

Learn more

The full flow documentation lives in the repository at docs/FLOWS.md.