Dispatching Workflows

When to use

• A phased plan exists (typically from ring:writing-plans) and you want each phase executed by a multi-agent harness, not a single subagent
• You want review and an adversarial contrarian pass baked inside every wave — verified work returns, unverified work does not
• Work benefits from phase checkpoints and supervisor course-correction between phases

Skip when

• One supervised subagent per wave is enough → ring:executing-plans (lighter; the supervisor reviews after the wave returns)
• Production work needing the full gated specialist roster and Gate 0/8/9 → ring:running-dev-cycle
• No plan exists yet → ring:writing-plans first
• Plan covers multiple independent subsystems → split into separate plans before executing

Sequence

Runs after: ring:writing-plans (consumes and updates its living plan document) Alternatives: ring:executing-plans (one supervised subagent per wave — lighter), ring:running-dev-cycle (full gated specialist cycle — heavier)

Related

Companion skills: ring:writing-plans (Task Format + phase-epic-task hierarchy used during elaboration), ring:test-driven-development (RED→GREEN per task, inside the harness), ring:committing-changes (closes each task with a signed atomic commit), ring:reviewing-code (the full 9+ reviewer pool — run it at plan close or for a high-stakes phase)