delegation-protocollisted

# Delegation Protocol ## The chain **Architect decides. Engineer implements. Quality verifies. Release ships.** Never skip a link. Implementation with no design decision produces rework. A release with no verification produces an incident. Both cost more than the link you skipped. ## Routing procedure 1. **Name the domain** in one sentence. If you need two sentences, it is two tasks — split first. 2. **Find the owner** in `.claude/teams/README.md`. 3. **Pick the minimum set.** One agent per distinct concern. Not one per file, not one per idea. 4. **Gather the declared Inputs** before delegating. An agent without its inputs guesses, and a confident guess is worse than an admitted gap. 5. **Delegate with context**, not with the user's raw prompt. State what was already decided, what is out of scope, and what you want back. 6. **Reconcile.** Where two agents disagree, do not average them. State the disagreement explicitly and escalate to the team's architect with both positions. ## Fan-out budget | Task | Agents | Why | |---|---|---| | One file, obvious fix | **0** — do it inline | Delegation costs more than the fix | | One feature, one domain | 1-2 | Implementer, then reviewer | | Cross-domain feature | 3-4, one per domain | Any more and they overlap | | System design | Architects first, implementers in a second pass | Design before build, always | More than four agents on one task means the task is not decomposed yet. Decompose it. ## Worked example > "Our c