agent-collaboration

Standardizes worktree awareness, decision recording, and cross-agent communication patterns for squad agents.

2|Updated Jul 24, 2026
One-click install
npx skills add https://github.com/elbruno/ElBruno.MagenticUI --skill agent-collaboration-elbruno
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-collaboration
Source: https://github.com/elbruno/ElBruno.MagenticUI/tree/main/.squad/templates/skills/agent-collaboration
Command: npx skills add https://github.com/elbruno/ElBruno.MagenticUI --skill agent-collaboration-elbruno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Multi-agent teams previously duplicated identical collaboration rules across every agent charter, creating redundant context and inconsistent behavior when recording decisions or requesting help from teammates. ## Core Features & Use Cases - Worktree Awareness: Resolves the repository root via the TEAM ROOT path from the spawn prompt, with a git rev-parse fallback, so agents never assume the current working directory. - Decision Recording: Writes team-affecting decisions as structured entries to the .squad/decisions/inbox/ drop-box instead of editing shared files directly. - Cross-Agent Communication & Reviewer Protocol: Routes requests for other agents through the coordinator and enforces that rejected work is revised by a different agent than the original author. - Use Case: A squad agent finishes a design decision affecting other teammates, writes a dated inbox entry with rationale, and flags in its response that the coordinator should bring in the reviewer. ## Quick Start Follow the agent-collaboration patterns to record your decision in the .squad decisions inbox and request input from another team member through the coordinator.

Frequently Asked Questions about agent-collaboration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Should agents read all team charters for context?▼

No. Agents only need their own charter context plus decisions.md. Reading all agent charters is an explicit anti-pattern that wastes context, and modifying other agents' history.md files is reserved for the Scribe role.