skills.rest
mpaulosky
mpauloskyCOMMUNITY
Explore all skills by this author →
GitHub

agent-collaboration

Standardize squad agent collaboration with worktree awareness and decision markdown files.

Updated Mar 18, 2022
Search Tags:#git#collaboration#squad#agent-communication#decision-logging#worktree-awareness#review-protocol
One-click install
npx skills add https://github.com/mpaulosky/dotfiles --skill agent-collaboration-mpaulosky
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-collaboration
Source: https://github.com/mpaulosky/dotfiles/tree/main/.copilot/skills/agent-collaboration
Command: npx skills add https://github.com/mpaulosky/dotfiles --skill agent-collaboration-mpaulosky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automated squad agents often duplicate collaboration rules, make assumptions about repository context, and mishandle decision records, causing missed coordination and conflicting edits. This Skill centralizes best-practice patterns so agents behave consistently around worktree awareness, decision recording, and cross-agent requests for help.

Core Features & Use Cases

  • Worktree awareness: Use the provided TEAM ROOT path for all repository-relative operations and fall back to git rev-parse --show-toplevel if TEAM ROOT is not available; never assume the current working directory is the repo root.
  • Decision recording: After making a team-impacting decision, write a markdown file to .squad/decisions/inbox/{your-name}-{brief-slug}.md with a dated title and metadata lines for By, What, and Why so others can discover and audit choices.
  • Cross-agent communication & reviewer protocol: If another agent's input is needed, explicitly request it so the coordinator can bring them in; if a reviewer rejects work, lock the original author out of revising and assign a different agent to perform the revision.
  • Anti-patterns to avoid: Do not read all charters unnecessarily, do not write directly to .squad/decisions.md, do not modify other agents' history.md files, and never assume CWD equals the repo root.

Quick Start

Use the agent-collaboration skill to write a decision file to .squad/decisions/inbox/yourname-slug.md summarizing the date, title, author, the decision, and the rationale.

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 in a shared git repository?▼

Multi-agent collaboration in a shared git repository is standardized by defining worktree awareness, decision recording, and cross-agent review protocols. Agents use a TEAM ROOT path or git rev-parse fallback to locate the repository and coordinate actions consistently.

How do AI agents record decisions in a squad workflow?▼

Decision recording in a squad workflow requires writing a markdown file to .squad/decisions/inbox/{name}-{slug}.md. The file must contain a dated title and metadata lines for By, What, and Why so other agents can discover and audit the choice.

Why should automated agents avoid assuming the current working directory is the repo root?▼

Assuming the current working directory is the repo root causes pathing errors in multi-agent workflows. Agents must use a provided TEAM ROOT path for repository-relative operations and fall back to git rev-parse --show-toplevel to guarantee correct worktree awareness.

What is the reviewer lock-and-assign protocol for cross-agent communication?▼

The reviewer lock-and-assign protocol dictates that if a reviewer rejects work, the original author is locked out from revising. A different agent is then assigned to perform the revision, ensuring objective cross-agent communication and resolving conflicts.

Can I write squad decisions directly to the main decisions.md file?▼

Writing squad decisions directly to .squad/decisions.md is an anti-pattern that bypasses the inbox workflow. Agents must write individual markdown files to .squad/decisions/inbox/ to maintain proper decision logging and prevent conflicting edits across the squad.

What are the limitations of modifying other agents' history.md files?▼

Modifying other agents' history.md files breaks squad workflow isolation and causes conflicting edits. Agents must never change another agent's history and should instead use the .squad/decisions/inbox/ directory for cross-agent communication and decision logging.

Related Skills

Explore More Software Engineering Skills→
usepowershellusepowershell
9

agent-collaboration

Standardize multi-agent collaboration with worktree awareness and decision logging.

Community
Intermediate
olivomarcoolivomarco
66

agent-collaboration

...

Community
Intermediate
QuintenpsQuintenps

agent-collaboration

Standardize cross-agent collaboration with decision logging and communication protocols.

Community
Intermediate
Soul-Brews-StudioSoul-Brews-Studio
116

worktree

Coordinate parallel git worktrees with Bash scripting to isolate agent workspaces.

Official
Basic