research

Parallel expert research launches up to 5 domain-specific agents to investigate codebase, web, docs, dependencies, and architecture simultaneously. A separate business-analyst then synthesizes these independent findings into a single, review-ready report.

Gathering diverse perspectives for a product feasibility study requires orchestrating independent data collection across multiple tracks. This approach prevents bias before a centralized reviewer synthesizes the findings into a comprehensive, structured report.

Yes, parallel swarm agents can investigate dependencies and docs simultaneously. The swarm coordinates up to 5 domain-specific tracks, including codebase, web, docs, dependencies, and architecture, to illuminate complex topics before implementation.

State persistence during phased expert research workflows saves scoped progress to survive context changes. This mechanism enables recovery across research phases, ensuring the final structured state and artifacts are suitable for downstream pipeline integration.

To trigger a multi-agent research swarm, you must define your topic and scope clearly. The swarm then runs parallel expert tracks across code, web, docs, dependencies, and architecture to generate a final, structured research report.

You should avoid parallel expert investigations when a topic lacks sufficient complexity to require multiple domain tracks. The swarm is designed for broad scoping across code, web, docs, and architecture, making it excessive for simple, single-domain validation tasks.