subagent-dispatch

Preventing conflicts in parallel coding subagents requires worktree isolation for each agent and resource serialization for shared access. This ensures each subagent operates independently in its own isolated environment while preventing concurrent editing issues.

Worktree isolation is a coordination mechanism ensuring each code-writing subagent operates in its own isolated environment. It prevents conflicts during parallel coding tasks by keeping agent changes physically separated until a safe merge.

Dispatching code-writing subagents requires invoking the skill with task details, completing a pre-dispatch checklist, and verifying builds and tests. This coordinates parallel tasks safely and ensures code changes pass linting before a final merge.

Yes, crash recovery handles failures from subagent tasks during parallel coding. The system manages recovery protocols to resume or safely rollback incomplete work without corrupting the isolated worktrees or the shared codebase.

Yes, post-dispatch cleanup automates the environment cleanup process after a parallel coding task is completed. This safely removes isolated worktrees and manages resources once the subagents finish their work.

Subagent coordination for code isolation is ideal for complex projects requiring parallel coding, such as large feature development or extensive bug fixes. It ensures efficient and safe collaboration when multiple agents modify code simultaneously.