agent-collaboration

Coordinate squad agents with worktree awareness and decision recording.

1|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/DeDuva/squad --skill agent-collaboration-deduva
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-collaboration
Source: https://github.com/DeDuva/squad/tree/main/.copilot/skills/agent-collaboration
Command: npx skills add https://github.com/DeDuva/squad --skill agent-collaboration-deduva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes collaboration patterns across all squad agents to ensure consistent worktree awareness, decision recording, and cross-agent communication.

Core Features & Use Cases

  • Worktree Awareness: Agents read TEAM ROOT and maintain consistent repo context to avoid drift.
  • Decision Recording: After decisions, write to .squad/decisions/inbox to ensure traceability and auditability.
  • Cross-Agent Communication: Alert and involve other agents when input or approval is required, coordinating through the coordinator.
  • Anti-Patterns: Avoid reading other agents' history.md and avoid editing others' artifacts directly to maintain clear ownership.

Quick Start

Integrate these collaboration patterns into your squad workflow to coordinate decisions and cross-agent communication.

Frequently Asked Questions about agent-collaboration

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

FAQPage Schema
How do I coordinate cross-agent communication in a shared repository worktree?

To coordinate cross-agent communication, standardize collaboration patterns by enforcing centralized decision recording and alerting other agents through a coordinator when input or approval is required. This ensures consistent worktree awareness and prevents context drift across the squad.

What is the best way to record decisions made by multiple squad agents?

The best way to record squad agent decisions is to write them to a centralized decisions inbox. This enforces traceability and auditability across the team workflow, ensuring all agents share consistent updates and historical context.

How does worktree awareness prevent repo context drift in multi-agent team workflows?

Worktree awareness prevents repo context drift by requiring agents to read a shared root reference and maintain a consistent repository context. This synchronization ensures all squad agents operate on the same baseline during cross-agent collaboration.

What anti-patterns should I avoid when standardizing multi-agent collaboration protocols?

When standardizing multi-agent collaboration protocols, avoid reading other agents' history files and never edit artifacts owned by others directly. These anti-patterns break clear ownership boundaries and disrupt the defined reviewer protocols.

Can I use cross-agent collaboration patterns for team-based development workflows without a coordinator?

No, these collaboration patterns require a coordinator to manage cross-agent communication. The coordinator routes alerts and approvals between squad agents, ensuring that worktree awareness and decision recording remain centralized and traceable.