agent-collaboration

Coordinate cross-agent collaboration with worktree awareness and decision logging.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardize collaboration across all squad agents by centralizing worktree awareness, decision logging, and cross-agent communication to reduce duplication and misalignment.

Core Features & Use Cases

  • Worktree awareness: rely on the TEAM ROOT to resolve .squad paths and keep agents synchronized.
  • Decision recording: after a decision, write it to .squad/decisions/inbox/{your-name}-{brief-slug}.md with date, author, decision, and rationale.
  • Cross-agent communication: request input from other agents via the coordinator; do not modify other agents' history.md.

Quick Start

Integrate these patterns into your spawn prompt and start recording decisions to the 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 cross-agent collaboration in a shared workspace?

Cross-agent collaboration is coordinated by standardizing worktree awareness, centralizing decision logging to a shared inbox, and routing inter-agent communication through a coordinator to prevent history conflicts.

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

Recording decisions requires writing a markdown file to the .squad/decisions/inbox directory, including the date, author, the specific decision, and its rationale to maintain alignment across agents.

How do agents share a workspace without overwriting each other's history?

Agents share a workspace by relying on the TEAM ROOT to resolve .squad paths and requesting input via the coordinator, ensuring they never modify another agent's history.md file directly.

Can I use a reviewer protocol to guard revisions in multi-agent environments?

Yes, a lightweight reviewer protocol is implemented to guard revisions, ensuring that changes are reviewed and inter-agent communication is properly managed through designated inbox paths.

Do I need spawn prompts to start standardizing cross-agent communication?

Integrating standardized patterns into your spawn prompts is required to initiate the protocol, allowing agents to synchronize worktree awareness and begin recording decisions immediately.

Why does cross-agent collaboration require a designated decisions inbox?

A designated decisions inbox is required to centralize decision logging, preventing duplication and misalignment by ensuring all agents submit dated markdown records with rationale to a shared location.