multi-agent-conflict

To prevent agent conflicts on the same branch, enforce pre-allocation conflict checks across git worktrees, active sessions, and worktree pools before allocating any new work to ensure safe coordination. It aborts allocation on conflict and provides auditable recovery procedures.

Pre-allocation conflict detection is a safety mechanism that coordinates git worktrees, agent sessions, and pool status to verify no other concurrent agent is actively using a target branch before work begins.

To recover stale worktrees and maintain shared workspace integrity, follow the built-in recovery guidance which provides actionable procedures to safely clean up abandoned worktrees and reset pool status.

Yes, this skill satisfies the requirement for mandatory abort-on-conflict workflows by stopping worktree allocation immediately when a conflict is detected, preventing concurrent agents from overwriting each other's work.

Git worktrees are the core mechanism used for allocation checks. This skill applies to any automation workflow where multiple agents may allocate worktrees across repositories, branches, or seats, requiring pool status coordination.