adaptive-agent-routing git:20261006.6a4c0f7A

Immutable. This exact content never changes and is served at /api/v1/blob/4e03502bce410b4e.

---
name: adaptive-agent-routing
description: Select the narrowest useful agent, skill, MCP, and config route for non-trivial work. Use when delegation, context placement, specialist ownership, duplicate skill aliases, or routing visibility materially affects execution; avoid for trivial single-surface work.
---

# Adaptive Agent Routing

Select routes by expected value, not by catalog match alone.

## Workflow

1. Classify the task shape and identify the smallest owning surface.
2. Read [global-working-agreements.md](references/global-working-agreements.md) only when the detailed route, specialist map, alias policy, or MCP boundary is relevant.
3. Preserve the active session's profile and model. Role files carry only the catalog worker `model`; they never pin reasoning effort, and spawns pass no model override.
4. Spawn an agent only when one of the four catalog conditions holds: an autoVerify routing profile matched and files changed, so its verifier runs before the task is reported done; independent parallel work exists; noisy logs or research should be isolated from the main thread; the user explicitly requests delegation. Skip trivial, strictly sequential, tightly coupled, and single-file work where delegation adds coordination cost.
5. When a request matches a routing profile, load the profile's auto-skill first (suggest it instead when it is explicit-only), and run the required verifier for autoVerify profiles after file changes. Start at most 2 agents per task without the user naming them; treat ten threads as capacity, not a target, and use at most four workers per task (a coordinator is not counted); more needs the user's explicit request.
6. Pick one of two routes, both at most two levels deep: Direct (the main session briefs one to four specialists) or Team (for a user-created board task, the main session briefs its coordinator, which briefs only its own cataloged workers). Workers never spawn; they name a needed role under Open questions as `needs: <role> - <why>`. Brief and check handoffs with the `agent-brief` skill.
7. Emit one `Routing plan:` update and one `Routing result:` summary instead of per-surface narration.
8. Keep destructive, credentialed, account, database, publish, deploy, and external-write actions approval-gated.

## Output Contract

Return selected and skipped surfaces, summarized evidence, commands run, and blockers. Do not paste raw agent transcripts or large logs.