orchestrate-parallel-work

You manage parallel task execution by decomposing complex workflows into independent sub-agents with explicit ownership. This approach prevents conflicts by assigning non-overlapping scopes and using optional worktree isolation to ensure task integrity.

The best way to decompose a large module is to split it into independent slices for parallel execution. This method allows individual agents to own specific work areas, facilitating smooth integration and reducing errors during development.

Worktree isolation provides an optional boundary that separates parallel processing tasks during execution. This mechanism ensures task integrity by allowing independent development and verification before explicit integration control is applied.

Yes, you need structured task definitions to run parallel execution across sub-agents. The system requires these definitions to establish clear ownership, verify task integrity, and manage explicit integration control for non-overlapping project scopes.

You should not use parallel task decomposition when project scopes overlap significantly or lack clear boundaries. This approach requires non-overlapping scopes and explicit integration control, making it unsuitable for tightly coupled or interdependent codebase areas.