Skip to content
cccskills
FreePublished on GitHub

agent-collaboration

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

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md2.0 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Shared hard rules enforced across all squad agents

The English summary is being prepared. Showing the original description.

github/gh-aw5.4KUpdated Oct 18, 2026

Route gh-aw design, creation, diagnosis, patching, active debugging, and upgrade requests to the right strategies.

The English summary is being prepared. Showing the original description.

github/gh-aw5.4KUpdated Oct 18, 2026

How to write comprehensive architectural proposals that drive alignment before code is written

The English summary is being prepared. Showing the original description.

github/gh-aw5.4KUpdated Oct 18, 2026

Upgrade gh-aw to latest gh-aw-firewall release and identify follow-up spec tasks.

The English summary is being prepared. Showing the original description.

github/gh-aw5.4KUpdated Oct 18, 2026

Review code that performs git or gh operations against repository checkouts in gh-aw, checking that the right credentials are available at the right time and that sparseness, shallowness and credential-free factors are properly considered.

The English summary is being prepared. Showing the original description.

github/gh-aw5.4KUpdated Oct 18, 2026

Defensive CI/CD patterns: semver validation, token checks, retry logic, draft detection — earned from v0.8.22

The English summary is being prepared. Showing the original description.

github/gh-aw5.4KUpdated Oct 18, 2026

See all skills by github

Report a problem with this skill