war-room-protocol

Multi-agent coordination without conflicts requires a shared war room workflow where agents check a mission board, claim tasks, and lock files before editing. This deterministic process prevents agents from overwriting each other's work in collaborative coding projects.

Preventing duplicate work with concurrent agents involves enforcing coordination rules through a mission board. Agents must check available tasks, claim them explicitly, and share findings so all agents stay aligned and track progress without repeating completed work.

File locking in a multi-agent workflow requires agents to call lock_file before editing, blocking other agents from modifying the same code. Agents release locks by calling complete_task when done, ensuring deterministic access control across shared repositories.

Yes, multi-agent task coordination requires a defined workflow with explicit functions like check_mission_board, claim_task, lock_file, share_finding, and complete_task, plus guidance documented in SKILL.md to keep all agents aligned.

You need a war room protocol for multi-agent code collaboration when several agents work on the same codebase across repositories simultaneously. It enforces the 7 Iron Rules to avoid conflicts, duplicate work, and overwriting each other's edits.

Mission board task management depends on agents strictly following the deterministic workflow and calling coordination functions correctly. If agents skip locking files or claiming tasks, the conflict prevention mechanism breaks down across the shared codebase.