agent-collaboration

Enforce standardized collaboration patterns for squad agents using .squad directories.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Worktree awareness: agents follow a shared reference point for repository structure and team roots.
  • Decision recording: write decisions to the inbox path under .squad/decisions/inbox/ with a clear header format.
  • Cross-agent communication: streamlined input requests routed through the coordinator to minimize miscommunication and delays.

Quick Start

Ask the coordinator to enforce the centralized collaboration patterns by ensuring agents read decisions.md and history.md and follow the inbox workflow.

Frequently Asked Questions about agent-collaboration

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

FAQPage Schema
How do I standardize cross-agent communication for a team workspace?

Standardizing cross-agent communication requires centralizing collaboration patterns so all squad agents route input requests through a coordinator, minimizing miscommunication and delays. The coordinator enforces this by ensuring agents read shared history files and follow a structured inbox workflow.

What is the best way to record agent decisions in a shared repository?

Recording agent decisions involves writing entries to the inbox path under .squad/decisions/inbox/ using a clear header format. This ensures all squad agents have a shared reference point for repository structure and team roots, eliminating duplicated guidance.

How does worktree awareness work for multi-agent collaboration?

Worktree awareness works by giving all squad agents a shared reference point for repository structure and team roots. This standardized pattern is enforced by the coordinator to ensure agents consistently understand the workspace layout during cross-agent communication.

Do I need a .squad directory to coordinate squad agents?

Yes, coordinating squad agents requires the presence of .squad directories and inbox/history files to guide execution. You also need coordinating spawn prompts to enforce the centralized collaboration patterns across the team-wide workspace.

Why does cross-agent communication fail without a centralized coordinator?

Without a centralized coordinator, cross-agent communication fails because agents lack standardized collaboration patterns, leading to duplicated guidance, inconsistent worktree awareness, and unrecorded decisions that cause miscommunication and delays.