agent-collaboration

To standardize cross-agent communication, codify worktree awareness, decision logging, and inbox-based messaging into a reusable spawn prompt pattern. This ensures squad agents coordinate input through a coordinator rather than working in isolation.

Agent decision logging requires writing a markdown file to `.squad/decisions/inbox/{your-name}-{brief-slug}.md`. This file must include the decision date, author, and rationale to inform teammates of changes affecting their work.

Worktree awareness is maintained by requiring agents to use the TEAM ROOT path provided in the spawn prompt. Agents must never assume the current working directory is the repository root to prevent file path errors.

No, you should request input through the coordinator instead of direct messaging. The inbox pattern is used for recording decisions, while the coordinator manages coordinated input from teammates to prevent isolation.

Agent collaboration anti-patterns include reading unrelated charters, modifying others' history.md files, and bypassing spawn prompts. Agents should strictly follow the standardized collaboration patterns to maintain team coordination.

Yes, a valid SKILL.md frontmatter with name and description is required. This enforces the functional requirements needed to enable consistent decision writing and cross-agent communication across the team.