agent-collaboration

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

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/codebytes/btt --skill agent-collaboration-codebytes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-collaboration
Source: https://github.com/codebytes/btt/tree/main/.copilot/skills/agent-collaboration
Command: npx skills add https://github.com/codebytes/btt --skill agent-collaboration-codebytes

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 practices for recording decisions and requesting help. ## Core Features & Use Cases - Worktree Awareness: Resolves the repository root via the TEAM ROOT path from the spawn prompt, falling back to git rev-parse --show-toplevel instead of assuming the current directory. - Decision Recording: Writes team-affecting decisions as structured entries to .squad/decisions/inbox/{name}-{slug}.md using a standard date/what/why format. - Cross-Agent Communication & Reviewer Protocol: Routes requests for other members through the coordinator and enforces that rejected work is revised by a different agent than the original author. - Use Case: An agent finishes a schema change affecting teammates, drops a decision file into the inbox, 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 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
How do I record a decision that affects other team members?

Write a markdown file to .squad/decisions/inbox/{your-name}-{brief-slug}.md containing the date, decision title, your name, what was decided, and why. Never write directly to .squad/decisions.md; always use the inbox drop-box.

How do I find the repository root in a multi-agent worktree setup?

Use the TEAM ROOT path provided in your spawn prompt, since all .squad/ paths are relative to it. If TEAM ROOT is missing, run git rev-parse --show-toplevel as a fallback rather than assuming the current working directory is the repo root.

How do agents request input from another team member?

State in your response that you need another member's input, and the coordinator will bring them in. Agents should not attempt work outside their own domain or read other agents' charters.

What happens when a reviewer rejects an agent's work?

The original author is locked out from revising that artifact, and a different agent must own the revision. The reviewer must state in the rejection response who should perform the revision.

What are the limitations of the decisions inbox approach?

The inbox is a drop-box only; agents must not write to the shared decisions.md directly or modify other agents' history.md files, which is Scribe's responsibility. It centralizes intake but relies on the coordinator for routing.