docs(agents): delegate substantive repository tasks

AGENTS.md

@@ -25,9 +25,15 @@ MCP service in one npm/Turborepo workspace.
    and prove the relevant compatibility contracts still hold. Preserve deployed
    interfaces and supported client behavior; repository checks alone do not
    prove a live change is safe.
-10. Scope work to the task. Route bounded implementation through the project
+10. Delegate every substantive repository task to at least one project agent so
-   `implementation` agent when delegation is useful; the primary agent retains
+   detailed exploration or execution stays out of the primary context.
-   acceptance, review, and final verification. Do not delegate trivial edits.
+   "Substantive" includes repository exploration, multi-file reasoning,
+   implementation, test execution, or contract/risk analysis. Use `repo_scout`
+   for read-only investigation and `implementation` for bounded changes; use
+   the additional roles according to `docs/agents/routing.md`. The primary
+   agent retains scope, acceptance, review, and the final answer. Skip
+   delegation only for trivial conversation, a single obvious lookup, or a
+   mechanical one-line edit whose coordination cost exceeds the work.
 11. Use high-effort reviewers only for the risk triggers in
    `docs/agents/routing.md`.
 

docs/agents/routing.md

@@ -1,9 +1,12 @@
 # Agent routing and effort
 
-The primary agent owns scope, acceptance criteria, task decomposition, and the
+The primary agent owns scope, acceptance criteria, task decomposition, review,
-final answer. Use one implementation agent when a bounded handoff will keep noisy
+and the final answer. Every substantive repository task must delegate at least
-execution out of the primary context. Do not pay the coordination cost for a
+one bounded unit to the best-fit project agent. Use `repo_scout` for read-only
-trivial one-file edit. Add other agents only for separable work or a risk trigger.
+discovery or analysis and `implementation` for product or harness changes. Add
+other agents only for separable work or the risk triggers below. Skip delegation
+only for trivial conversation, a single obvious lookup, or a mechanical one-line
+edit whose coordination cost exceeds the work.
 
 ## Implementation and integration