agent-collaboration

Standardize worktree awareness, decision recording, and cross-agent communication across squad agents.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often suffer from inconsistent collaboration patterns across multiple agents, leading to miscommunication and duplicated work. This Skill centralizes worktree awareness, decision recording, and cross-agent communication into a single, shared protocol.

Core Features & Use Cases

  • Worktree awareness: agents reference the TEAM ROOT path reliably and avoid assuming the current working directory.
  • Decision recording: standardized spots and formats for logging decisions to preserve context and enable auditing.
  • Cross-agent communication: prompts coordination when input from other agents is required, preventing silos and delays.

Quick Start

Integrate the centralized collaboration patterns into your agent workflow to harmonize worktree awareness, decision recording, and cross-agent communication.

Frequently Asked Questions about agent-collaboration

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

FAQPage Schema
How do I standardize multi-agent collaboration on a shared codebase?

Multi-agent collaboration is standardized by centralizing worktree awareness, decision recording, and cross-agent communication into a shared protocol to reduce miscommunication and duplicated effort.

How do I record agent decisions to preserve context and enable auditing?

Agent decisions are recorded by writing them to a .squad/decisions/inbox directory, ensuring consistent governance, traceability, and preserved context across the team workflow.

How does cross-agent communication work in chartered workflows?

Cross-agent communication prompts coordination when input from other agents is required, preventing silos and delays by requiring coordinators to provide spawn prompts directing agents to read shared history and decision files.

Why do my agents assume the wrong working directory in a shared codebase?

Agents assume the wrong directory due to lacking worktree awareness; this is fixed by having agents reliably reference the TEAM ROOT path instead of assuming the current working directory.

Do I need a coordinator to manage agent communication and decision recording?

A coordinator is required to provide spawn prompts that direct agents to read decisions.md and history.md, ensuring agents follow the standardized governance and traceability protocol.

What's the best way to prevent duplicated effort across multiple agents?

The best way to prevent duplicated effort is applying a centralized squad collaboration protocol that standardizes decision logging and cross-agent communication across chartered workflows.