agent-orchestra

From the author

Use when three or more AI agents are available and a task needs coordinated execution, or when work must be handed to another agent, session or tool. It ships the coordination rules as ENFORCED invariants rather than advice: one writer per resource (a conflicting claim is refused and names the holder), a verifier that is never the implementer and whose PASS must carry criterion-linked evidence, a failed verification that blocks both done and dispatch to evidence, three failed rounds that block the task outright, an external action that cannot be dispatched until an approval covering it is recorded, a domain review by a third party for consequential work, rigorous E1-E4 evidence grading with enforced floors, capability-scored role assignment from a roster of any size (any agent names), a shared handoff record with a checker, a dependency-free task-queue CLI, an important-task intake gate, and a coordination anti-pattern guide. One command - scripts/gate.mjs - runs sixteen checks and injects twelve known faults