agent-collaboration

Cross-agent collaboration is coordinated by standardizing communication through a central coordinator, ensuring agents use inbox-based decision workflows and explicit cross-agent prompts to prevent miscommunication.

Recording decisions across multiple agents requires publishing decisions to an inbox at .squad/decisions/inbox/{your-name}-{brief-slug}.md, using standard formatting to maintain consistent governance and history.

Worktree awareness is managed by coordinating with TEAM ROOT rules, explicitly preventing agents from incorrectly assuming the current working directory is the repository root.

Agents should avoid writing directly to others' history files because it creates an anti-pattern; instead, they must use the centralized inbox system to request input and route updates through the coordinator.

Yes, this multi-agent workflow requires a central coordinator to handle governance via a reviewer protocol, route explicit cross-agent communication, and enforce deterministic task guidance.

You need centralized patterns for multi-agent team workflows when duplicated collaboration behaviors cause redundancy, requiring standardization for worktree awareness, decision recording, and cross-agent communication.