summon-team-build

Parallel software development workflows are coordinated by spawning a four-member team—Fetcher, Planner, Builder, and Checker—to work simultaneously. This orchestration produces shared research, a blueprint, implementation, and QA review deliverables.

The best way to generate a project blueprint and implementation simultaneously is using an orchestrated team build. A Fetcher agent gathers context while a Planner drafts the blueprint and a Builder writes the implementation in parallel.

Four-agent team orchestration works by loading shared context from Brief.md and Rules.md, then assigning specialized roles. The Fetcher researches, the Planner designs, the Builder implements, and the Checker performs QA review in parallel.

Yes, you need shared context files to run parallel work effectively. The orchestration requires loading a Dashboard Brief.md for task alignment and a Library Rules.md file to guide the implementation and review workflows.

Yes, you can use team orchestration for both project management and QA review. The process inherently includes a Planner for project management blueprinting and a Checker dedicated to executing the quality review phase.

You should avoid launching a parallel team build if your redevelopment task lacks sufficient complexity to warrant four agents. Simple bug fixes or isolated edits do not require the shared dashboards and coordinated workflows this orchestration provides.