agent-collaboration

Standardize squad agent collaboration with worktree awareness and decision recording.

49|6|Updated Aug 24, 2021

Search Tags:#collaboration #multi-agent #worktree #inbox #history #cross-agent #decision-recording

Ready to run

npx skills add https://github.com/webmaxru/bpm-counter --skill agent-collaboration-webmaxru

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: agent-collaboration
Source: https://github.com/webmaxru/bpm-counter/tree/main/.copilot/skills/agent-collaboration
Command: npx skills add https://github.com/webmaxru/bpm-counter --skill agent-collaboration-webmaxru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standard collaboration patterns for all squad agents to ensure worktree awareness, consistent decision recording, and reliable cross-agent communication.

Core Features & Use Cases

Worktree Awareness: Agents follow shared worktree conventions and reference the TEAM ROOT to avoid context drift.
Decision Recording: After a decision that affects others, write it to .squad/decisions/inbox/{your-name}-{brief-slug}.md with the date, author, rationale, and outcome.
Cross-Agent Communication: If input is needed, request input via the coordinator; decisions.md and history.md provide traceability and audit trails.

Quick Start

Instruct agents to adopt the centralized collaboration patterns for worktree awareness, decisions, 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 cross-agent communication for a multi-agent team?▼

You can standardize cross-agent communication by applying shared worktree conventions, routing input requests through a coordinator, and recording outcomes to decisions.md and history.md for reliable traceability.

What is the best way to record decisions in a shared worktree environment?▼

The best way to record decisions is to write a markdown file to the inbox directory with the date, author, rationale, and outcome, ensuring all squad agents maintain worktree awareness and consistent audit trails.

How do agents coordinate worktree handoffs without context drift?▼

Agents coordinate handoffs by referencing the shared TEAM ROOT and utilizing inbox-based decision recording to request help, ensuring cross-agent communication remains traceable and prevents context drift.

When do I need an inbox-based decision recording workflow for multi-agent collaboration?▼

You need an inbox-based decision recording workflow when multiple agents operate across shared worktrees and any decision affects other agents, requiring standardized context patterns and history.md traceability.

Can I use centralized collaboration patterns for agents requesting help from each other?▼

Yes, you can use centralized collaboration patterns to request input via the coordinator, which references decisions.md and history.md to ensure reliable cross-agent communication and structured handoffs.

Why does multi-agent context drift happen in shared worktrees and how do I prevent it?▼

Context drift happens when agents lose awareness of shared worktree states, which you prevent by adopting centralized collaboration patterns that enforce referencing the TEAM ROOT and standardized decision recording.