agent-collaboration

Coordinate squad agents' worktree awareness, decision recording inboxes, and reviewer protocols.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/Leep-GH/Lee-s-squad --skill agent-collaboration-leep-gh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-collaboration
Source: https://github.com/Leep-GH/Lee-s-squad/tree/main/.copilot/skills/agent-collaboration
Command: npx skills add https://github.com/Leep-GH/Lee-s-squad --skill agent-collaboration-leep-gh

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: 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.
  • Decision Recording: After making a decision that affects other team members, write it to: .squad/decisions/inbox/{your-name}-{brief-slug}.md with a standard format: Date: referenced date, Title: referenced decision title, By: your name, What: description of the decision, Why: rationale.
  • Cross-Agent Communication: If you need input, say so in your response; the coordinator will bring them in. Don't try to do work outside your domain.

Quick Start

Adopt the standardized collaboration pattern across all squad agents for your current project.

Frequently Asked Questions about agent-collaboration

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

FAQPage Schema
How do I coordinate decisions across multiple AI agents in a squad workflow?

To coordinate decisions across multiple agents, standardize cross-agent collaboration patterns using worktree awareness and an inbox-based decision recording protocol. This ensures predictable decision flow, input requests, and coordinated actions among team members.

What is the best way to record decisions that affect other agents in a multi-agent build?

The best way to record decisions affecting other agents is writing to the `.squad/decisions/inbox/{your-name}-{brief-slug}.md` file path. This standard format logs the date, title, author, decision description, and rationale for predictable team coordination.

How do squad agents handle git worktree paths during cross-agent collaboration?

Squad agents handle git worktree paths by using the TEAM ROOT path provided in the spawn prompt, keeping all `.squad/` paths relative to this root. If TEAM ROOT is missing, agents run `git rev-parse --show-toplevel` as a fallback.

Does cross-agent collaboration require a specific reviewer protocol for edits?

Yes, cross-agent collaboration requires a clear reviewer protocol to guard against unauthorized edits and miscommunication. Agents must request input via their response so the coordinator can bring in other members, preventing work outside their domain.

Why should I not assume the current working directory is the repository root in team workflows?

You should not assume the current working directory is the repository root because cross-agent collaboration relies on accurate worktree path handling. Assuming CWD breaks standardized `.squad/` relative paths and disrupts coordinated actions across the team.