delegation

Subagent delegation requires constructing consistent delegation prompts that enforce pre-work protocols. You inject base agent protocols and filesystem safety rules, then include all required downstream_context blocks to maintain alignment across phases.

A downstream_context block is a structured data segment propagated from one phase to the next. It maintains alignment by ensuring subsequent subagents receive the required context from previous phases or explicit placeholders for missing dependencies.

You enforce filesystem safety by injecting strict scope boundaries and absolute file path requirements into every delegation prompt. This prevents unsafe modifications and ensures all subagent outputs are predictable and auditable.

Yes, structured templates and decision rules guide subagents through deterministic task execution. These templates enforce clear handoffs, downstream consumer declarations, and explicit validation steps for predictable outputs.

Manual context propagation often leads to missing downstream_context blocks and inconsistent pre-work formatting. Without enforced protocol injection, subagents lose alignment across phases, resulting in unauditable outputs and unsafe file modifications.