원클릭으로
agent-collaboration
Standard collaboration patterns for all squad agents — worktree awareness, decisions, cross-agent communication
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Standard collaboration patterns for all squad agents — worktree awareness, decisions, cross-agent communication
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | agent-collaboration |
| description | Standard collaboration patterns for all squad agents — worktree awareness, decisions, cross-agent communication |
| domain | team-workflow |
| confidence | high |
| source | extracted from charter boilerplate — identical content in 18+ agent charters |
Every agent on the team follows identical collaboration patterns for worktree awareness, decision recording, and cross-agent communication. These were previously duplicated in every charter's Collaboration section (~300 bytes × 18 agents = ~5.4KB of redundant context). Now centralized here.
The coordinator's spawn prompt already instructs agents to read decisions.md and their history.md. This skill adds the patterns for WRITING decisions and requesting help.
Use the TEAM ROOT path provided in your spawn prompt. All .squad/ paths are relative to this root. If TEAM ROOT is not provided (rare), run git rev-parse --show-toplevel as fallback. Never assume CWD is the repo root.
After making a decision that affects other team members, write it to:
.squad/decisions/inbox/{your-name}-{brief-slug}.md
Format:
### {date}: {decision title}
**By:** {Your Name}
**What:** {the decision}
**Why:** {rationale}
If you need another team member's input, say so in your response. The coordinator will bring them in. Don't try to do work outside your domain.
If you have reviewer authority and reject work: the original author is locked out from revising that artifact. A different agent must own the revision. State who should revise in your rejection response.
.squad/decisions.md — always use the inbox drop-boxShared hard rules enforced across all squad agents
How to write comprehensive architectural proposals that drive alignment before code is written
Defensive CI/CD patterns: semver validation, token checks, retry logic, draft detection — earned from v0.8.22
Platform detection and adaptive spawning for CLI vs VS Code vs other surfaces
Coordinating work across multiple Squad instances
How to coordinate with squads on different machines using git as transport