agentleFS
GitHubKnown publishergithub/squad/.copilot/skills/agent-collaboration/SKILL.md

agent-collaboration

Skill3.4k starsChanged 2 months agoMITView on GitHub

Standard collaboration patterns for all squad agents — worktree awareness, decisions, cross-agent communication

11 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use personal-squad.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 6 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every agent on the team follows identical collaboration patterns for worktree awareness, decision recording, and cross-agent communication.

    line 11
  2. Very specific:

    Use the TEAM ROOT path provided in your spawn prompt.

    line 18
  3. Very specific:

    After making a decision that affects other team members, write it to: .squad/decisions/inbox/{your-name}-{brief-slug}.md

    line 21
  4. Distinctive:

    If you need another team member's input, say so in your response.

    line 33
  5. Distinctive:

    If you have reviewer authority and reject work: the original author is locked out from revising that artifact.

    line 36
  6. Distinctive:

    Don't read all agent charters — you only need your own context + decisions.md

    line 39
  7. Very specific:

    Don't write directly to .squad/decisions.md — always use the inbox drop-box

    line 40
  8. Distinctive:

    Don't modify other agents' history.md files — that's Scribe's job

    line 41
  9. Distinctive:

    Don't assume CWD is the repo root — always use TEAM ROOT

    line 42

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Context

Every agent on the team follows identical collaboration patterns for worktree awareness, decision recording, and cross-agent communication. These were previously duplicated in every charter's Collaboration section (~300 bytes × 18 agents = ~5.4KB of redundant context). Now centralized here.

The coordinator's spawn prompt already instructs agents to read decisions.md and their history.md. This skill adds the patterns for WRITING decisions and requesting help.

Patterns

Worktree Awareness

Use the TEAM ROOT path provided in your spawn prompt. All .squad/ paths are relative to this root. If TEAM ROOT is not provided (rare), run git rev-parse --show-toplevel as fallback. Never assume CWD is the repo root.

Decision Recording

After making a decision that affects other team members, write it to: .squad/decisions/inbox/{your-name}-{brief-slug}.md

Format:

### {date}: {decision title}
**By:** {Your Name}
**What:** {the decision}
**Why:** {rationale}

Cross-Agent Communication

If you need another team member's input, say so in your response. The coordinator will bring them in. Don't try to do work outside your domain.

Reviewer Protocol

If you have reviewer authority and reject work: the original author is locked out from revising that artifact. A different agent must own the revision. State who should revise in your rejection response.

Anti-Patterns

  • Don't read all agent charters — you only need your own context + decisions.md
  • Don't write directly to .squad/decisions.md — always use the inbox drop-box
  • Don't modify other agents' history.md files — that's Scribe's job
  • Don't assume CWD is the repo root — always use TEAM ROOT

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.