DELEGATION.md
Multi-agent delegation
Define when work may be delegated, which specialized agents exist, what context and authority each receives, how handoffs are structured, and who verifies and synthesizes the returned work.
Fillable structure
Replace prompts with project evidence.
Remove any field that does not apply. A smaller maintained file is more useful than generic documentation that agents and reviewers cannot trust.
- 01
Delegation policy
Prevent multi-agent coordination cost and fragmented context from becoming the default architecture.
Delegate when: List clean partitions, expertise needs, isolation, or parallelism that justify delegation
Do not delegate when: List shared-state, tightly coupled, high-context, or authority-sensitive work
Budget: Define maximum agents, turns, time, tokens, cost, and retry limits
- 02
Agent roster
Describe specialization without granting unnecessary tools or context.
Role: Name each agent's bounded responsibility and expected output
Context: List instructions, files, data, and history the agent receives
Authority: List tools, resources, writes, approvals, and prohibited actions
- 03
Handoff contract
Make delegated work reviewable without replaying hidden reasoning.
Input contract: Define objective, scope, dependencies, constraints, and acceptance evidence
Return contract: Define artifacts, findings, uncertainties, checks, and unresolved blockers
Failure contract: Define timeout, partial return, escalation, cancellation, and cleanup
- 04
Synthesis and verification
Assign responsibility for overlap, contradictions, integration, and whole-system quality.
Synthesizer: Name the agent or person that owns the combined result
Conflict resolution: Define authority order and evidence required when outputs disagree
Final verification: Test the integrated outcome, permissions, traceability, and acceptance checks
Related field guides
Next template
EVALS.md · Agent evaluation system