agent-collaboration

To track decisions across multiple agents, you standardize recording by writing markdown files to a shared inbox at .squad/decisions/inbox/. This ensures cross-agent communication and rationale are consistently documented.

Prevent working directory conflicts by enforcing worktree awareness, which roots all agent paths to a shared TEAM ROOT. This avoids incorrect working-directory assumptions when multiple agents operate simultaneously.

Manage reviewer ownership by following a strict reviewer protocol that defines safe revision ownership. This prevents locked artifacts from being edited by the original author after rejection.

Yes, you can coordinate help requests between autonomous agents by standardizing cross-agent communication. Agents request help and document dependencies without stepping outside each agent's domain.

Decisions impacting other team members should use a specific markdown schema. Files must be named {your-name}-{brief-slug}.md and dropped into the .squad/decisions/inbox/ directory for consistent processing.

You need to standardize collaboration boilerplate to eliminate duplicated effort across agents. This ensures consistent worktree tracking, decision recording, and help requests during multi-agent workflows.