orchestrate
Orchestrate
This skill decides what each worker does next and launches it safely. The core
move: send free capacity to finished work that still owes checks, integration
or a judgment before starting anything new, and launch nothing until every
packet in the batch is valid with canonical write scopes that do not collide.
It worked when no finished-but-unchecked candidate waits while new work starts,
no task runs on a closed but unintegrated prerequisite, no two launched workers
share a canonical path or a contended resource, and each packet has a result
naming observed engagement, terminal status and not_as_briefed.
One agent and one writer is the default. Give work to parallel workers only where the pieces are independent: disjoint canonical write scopes and no contended runtime resource. Dependent or overlapping work stays with one writer or runs in sequence. Within that, concurrency follows the observed bottleneck: reserve capacity for integration, review and repair, and reduce new starts while candidates accumulate.