One-click install
npx skills add https://github.com/olivomarco/vbd-copilot --skill agent-collaboration-olivomarco
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-collaboration
Source: https://github.com/olivomarco/vbd-copilot/tree/main/.copilot/skills/agent-collaboration
Command: npx skills add https://github.com/olivomarco/vbd-copilot --skill agent-collaboration-olivomarco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Every agent on the team follows identical collaboration patterns for 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. Never assume CWD is the repo root. If TEAM ROOT is not provided, run git rev-parse --show-toplevel as a fallback.
  • Decision Recording: After making a decision that affects other team members, write it to .squad/decisions/inbox/{your-name}-{brief-slug}.md with a header that includes date, author, and rationale.
  • Cross-Agent Communication: If you need input from another agent, request it in your response and let the coordinator bring them in; avoid performing work outside your domain.
  • Anti-Patterns: Do not read every agent charter; do not write directly to decisions.md; do not modify other agents' history.md; always rely on the inbox for decisions.

Quick Start

Adopt the centralized collaboration patterns by using TEAM ROOT, reading decisions.md, and writing decisions to .squad/decisions/inbox.

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 agents in a shared worktree?

You coordinate decisions across multiple agents by writing them to a shared .squad/decisions/inbox directory using a standardized format, ensuring all squad members reference the same TEAM ROOT path for worktree awareness.

What is the best way to record agent decisions so other team members can read them?

The best way to record agent decisions is writing markdown files to the .squad/decisions/inbox drop-box with headers containing date, author, and rationale, preventing direct modifications to decisions.md.

How does cross-agent communication work when an agent needs input from another agent?

Cross-agent communication works by requesting input in your response and letting the coordinator bring the other agent in, avoiding direct work outside your domain instead of agents talking directly to each other.

Why should agents avoid reading every agent charter and modifying other agents' history?

Agents should avoid reading every agent charter and modifying history because it creates conflicts and violates safe operation rules; agents must always rely on the inbox drop-box for decisions.

Can I use this collaboration protocol if TEAM ROOT is not provided in the spawn prompt?

Yes, you can use this collaboration protocol if TEAM ROOT is not provided by running git rev-parse --show-toplevel as a fallback to locate the repository root for all .squad/ relative paths.

What are the limitations of using a centralized inbox for multi-agent coordination?

The limitations of using a centralized inbox include the inability to write directly to decisions.md, edit other agents' history.md, or perform work outside your domain, requiring a coordinator to involve other agents.