Agent Swarms & Dispatch Chain

Multi-agent orchestration featuring Design PMs, Planning PMs, Implementation PMs, QA PMs, and Deployment PMs coordinating autonomously across your engineering lifecycle.

Dispatch

Work is routed, not assigned

A scope classifier reads the change and picks the specialists it needs. No standing team and no idle agents — the roster is assembled per wave and dissolved when the wave closes.

wos:dispatch
$ wos dispatch --range HEAD~1..HEAD
scope api · migration · contract
confidence high
roster backend · postgres · contract-architect
wave w1 — 3 units, no file overlap
✔ dispatched in 11ms

The chain

Five phases, each owned by a PM agent

Every change moves design to plan to build to review to deploy. The phase boundary is where context is handed over, and nothing crosses it unrecorded.

01

Design PM

Requirements intake, PRD authoring and design-token extraction.

02

Planning PM

Decomposes the PRD into units, maps dependencies, sizes the waves.

03

Implementation PM

Runs the build wave with file-overlap checks and spec-drift enforcement.

04

QA PM

Tiered review: contracts, then blast radius, then signed ratification.

Handover

Context survives the phase boundary

Each PM writes a signed artefact the next phase reads. A wave that fails review comes back with its findings attached, so the rebuild starts from evidence rather than a fresh guess.

wave signoff
wavew3 — 4 units
units committed4 / 4
findings2 auto-resolved, 1 pending
contract driftnone
signoff nonce0x8f2a…c91d
110+

Specialist workers

<12ms

Dispatch latency

5

Autonomous phases

4

Parallel builders