delegate-worklisted

# Delegate Work Use the smallest useful team. Delegate to protect the main context or gain independent specialist evidence, not to imitate an organization chart. ## Confirm Authority and Value Delegate only after a direct user request or an applicable instruction explicitly authorizes it. Otherwise continue with the main task even when parallel work appears possible. Before spawning an agent, require a bounded lane that offers at least one concrete benefit: 1. independent read-heavy exploration can run in parallel; 2. a specialist can assess a distinct risk surface; 3. implementation can have exclusive file or module ownership; 4. an independent verifier can challenge the integrated result; 5. noisy logs, broad searches, or experiments would pollute the main context. Keep work in the main task when it is trivial, sequential, decision-heavy, tightly coupled, likely to touch the same files, or cheaper to complete than to specify and integrate. More agents are not evidence of a better process. Read `references/agent-routing.md` before selecting roles. Read `references/task-contracts.md` before spawning agents. Read `references/orchestration.md` for three or more lanes, dependent waves, or shared-workspace risks. ## Keep the Main Task in Control The main task owns: 1. the user's outcome, scope, constraints, and authority; 2. material product and architecture decisions; 3. the dependency graph and assignment boundaries; 4. synthesis, conflict resolution, and final edits;