skills.rest
elbruno
elbrunoCOMMUNITY
Explore all skills by this author →
Website𝕏@elbrunoGitHub

cross-squad-communication

Coordinates queries, task delegation, and context sharing between independent Squad instances across repositories.

2|Updated Jul 24, 2026
Search Tags:#multi-agent#github issues#task delegation#squad#async communication#copilot cli#cross-repository
One-click install
npx skills add https://github.com/elbruno/ElBruno.MagenticUI --skill cross-squad-communication-elbruno
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cross-squad-communication
Source: https://github.com/elbruno/ElBruno.MagenticUI/tree/main/.squad/templates/skills/cross-squad-communication
Command: npx skills add https://github.com/elbruno/ElBruno.MagenticUI --skill cross-squad-communication-elbruno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When multiple repositories each run their own Squad (AI team), there is no shared runtime, MCP tools, or issue tracker between them. This Skill provides concrete protocols for exchanging knowledge queries, PR reviews, task delegations, and dependency analysis across those isolated squads. ## Core Features & Use Cases - Four communication patterns: synchronous Copilot CLI sessions (Pattern 0), read-only metadata queries (Pattern 1), git-based async requests (Pattern 2), and GitHub issue-based delegation (Pattern 3), with a decision tree for choosing between them. - Liveness monitoring: log-directory-based stall detection and recovery actions for long-running CLI sessions with slow MCP server initialization. - Structured request/response formats: YAML schemas for cross-squad requests and responses, plus a platform compatibility matrix covering GitHub Issues, Azure DevOps, and Planner. - Use Case: A research squad needs the platform squad's architecture decisions. It reads the peer's .squad/decisions.md directly for a quick answer, or spawns copilot -C <repo> --agent squad for deeper analysis, or files a labeled GitHub issue when the repo is not cloned locally. ## Quick Start Ask the agent to query a peer squad's architecture by reading its .squad/team.md and decisions.md files, or by spawning a Copilot CLI session with --agent squad against the target repository.

Frequently Asked Questions about cross-squad-communication

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

FAQPage Schema
How do I send a query to another Squad-enabled repository?▼

Spawn a Copilot CLI session with the working directory set to the target repo: copilot -C <targetRepo> --agent squad -p <prompt>. The --agent squad flag is required so the session loads the peer's coordinator, team.md, and MCP tools instead of a generic session.

How do I choose between synchronous CLI and async git-based requests?▼

Use the synchronous CLI pattern for quick knowledge queries when the target repo is cloned locally. Use git-based async requests when work must persist as artifacts, takes multiple cycles, or when the target repo is not available locally.

Does cross-squad communication work with Azure DevOps instead of GitHub?▼

Yes, but issue-based delegation (Pattern 3) only works on GitHub. For Azure DevOps or mixed platforms, use the git-based async pattern (Pattern 2), which is the universal fallback documented in the platform compatibility matrix.

Why does my synchronous CLI session appear to time out?▼

MCP server initialization and .squad metadata loading can take 30-60 seconds, so fixed timeouts kill valid sessions. Monitor the session log directory for activity instead, and retry with --disable-builtin-mcps for lightweight queries.

What happens if the target squad's Ralph is not running?▼

Async requests (Patterns 2 and 3) will never be processed without Ralph monitoring the target repo. Check for recent Ralph commits before sending async requests, or fall back to the synchronous CLI pattern.

Related Skills

Explore More Software Engineering Skills→
DeDuvaDeDuva
1

init-mode

Propose a team roster and create a .squad directory after user confirmation.

Community
Advanced
jedrecordjedrecord

hal

Routes incoming requests to appropriate AI team members via Agent protocol.

Community
Advanced
githubnextgithubnext
5.1k

cross-squad-communication

Coordinates queries, task delegation, and context sharing between independent Squad instances across repositories.

Official
Advanced
lbouriezlbouriez

agent-collaboration

Automate squad agent collaboration with shared worktree awareness and decision recording.

Community
Intermediate