delegate-first

Delegate by default to preserve main context during multi-step operations. Before executing directly, verify file paths and output size; if uncertainty exists about scope or predictability, use Task tools to delegate heavy work to subagents instead of consuming main context.

Delegate when starting multi-step operations, when scope is uncertain, or when direct execution might exhaust context. Apply absolute certainty checks before any operation—if you cannot guarantee exact file paths and predictable steps, delegate via Task to keep main context lean.

Use strategic delegation as a behavioral principle for context preservation. Decide before acting by confirming exact file paths and output size; when certainty is not guaranteed, delegate operations to subagents rather than executing them in main context to maintain stability.

Delegation prevents context exhaustion by offloading heavy work to subagents while keeping main context available for decision-making and coordination. This approach complements task optimization by ensuring each operation's scope is verified before execution and uncertain operations are handled separately.

Yes. Delegation is designed for scenarios where scope is uncertain or direct execution risks context exhaustion. Before acting, verify file paths and predictability; if either cannot be confirmed absolutely, delegate the operation to a subagent via Task tools to preserve main context stability.

Delegation requires absolute certainty checks before any operation—you must still verify exact file paths and output predictability upfront. Unnecessary delegation wastes coordination overhead; delegate only when scope is uncertain, multi-step complexity is high, or main context exhaustion is a genuine risk.