workflow-routing

Route code tasks to the right workflow by using a decision matrix that matches task type, difficulty, and risk level to appropriate planning, implementation, and review pipelines. This matrix categorizes tasks into A/B/C/D/E/Mini workflows to prevent wasted cost and avoid one-size-fits-all pipelines.

Orchestrate pull requests by selecting a specific workflow route based on the task pattern, such as utilizing dedicated paths for hotfixes, mechanical refactors, or SPEC/ADR decisions. This prevents the anti-pattern of switching workflows mid-PR and ensures proper role separation.

Ensure role separation for high-stakes invariant changes by applying a routed workflow that mandates distinct planner, implementer, and reviewer responsibilities. This workflow includes triple-review or equivalent high-diversity guardrails to reduce the chance that a single model misses critical edge cases.

Manage multi-agent isolation and quota fallback by applying elastic routing logic that includes quota-aware downgrades, such as reducing Opus or Codex usage. This enforces isolation rules for parallel agents when model quotas are constrained.

You need a triple-review workflow for algorithmic correctness work when the task involves high-stakes invariant changes that require high-diversity review. Routing via a diverse planning, implementation, and final confirmation path reduces the risk of any single model missing critical edge cases.