delegation-principle

To delegate AI agent tasks, use the Task tool to route work to specialized subagents with explicit types. This enforces a coordinator role for the main agent, ensuring clear handoffs and context-preserving execution across planning, design, and implementation phases.

AI agent orchestration is managing workflows by delegating tasks to subagents rather than implementing them directly. You need it when maintaining a coordinator role for clear handoffs, ensuring the main agent prevents direct code modifications and preserves execution context.

Yes, you can prevent the main AI agent from modifying source code by enforcing delegation through the Task tool. This skill restricts the main agent to a coordinator role, routing all direct implementation and modifications to specialized subagents.

You maintain clear handoffs across planning, design, and execution by delegating work to subagents via the Task tool. This delegation-first workflow ensures auditability and safety through traceable boundaries between each orchestration phase.

Yes, the delegation workflow supports rapid, context-preserving task execution by routing work to subagents through the Task tool. This approach maintains clear coordination boundaries while ensuring specialized agents handle implementation efficiently.

A limitation of this delegation-first workflow is that the main agent is strictly restricted from implementing tasks or modifying code directly. All execution must be routed through the Task tool to subagents, preventing direct intervention if subagent delegation fails.