copilot-delegate-subagent

Parallel subagent orchestration in the GitHub Copilot CLI breaks down large workflows into independent subtasks. You define specific delegation patterns like direct or fleet execution to run concurrent processes, such as frontend and backend development, for faster task completion.

Task decomposition for specialized agent utilization is breaking down large, complex workflows into smaller, manageable subtasks. This allows you to assign specific components to agents with targeted expertise, ensuring focused and efficient execution of complex software engineering projects.

Yes, you can run multiple independent subagents concurrently for task decomposition. The parallel execution pattern speeds up overall task completion by assigning distinct subtasks, like UI implementation and database schema design, to different specialized agents running at the same time.

Available delegation patterns for subagent orchestration in Copilot CLI include direct, fleet, and sequential execution. These patterns enable efficient task decomposition and result aggregation, supporting both focused and parallel workflows for complex software engineering projects.

Subagent delegation requires the GitHub Copilot CLI environment and clear definition of tasks, delegation patterns, and result integration strategies. No additional dependencies are required, but you must provide structured task definitions to ensure successful parallel or focused execution.

You should avoid parallel subagent execution for task decomposition when subtasks are tightly coupled or depend on each other's immediate output. Without clear task boundaries and independent result integration strategies, fleet or parallel execution may complicate workflow orchestration.