cross-squad

Coordinates work delegation and discovery across multiple Squad instances using manifests and GitHub issues.

1|Updated Jul 7, 2026
One-click install
npx skills add https://github.com/seiggy/maf-copilot-studio-demo --skill cross-squad-seiggy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cross-squad
Source: https://github.com/seiggy/maf-copilot-studio-demo/tree/main/.squad/templates/skills/cross-squad
Command: npx skills add https://github.com/seiggy/maf-copilot-studio-demo --skill cross-squad-seiggy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an organization runs multiple Squad instances across different repositories, agents lack a standard way to discover each other, share context, and hand off work without creating tight coupling or leaking internal state. ## Core Features & Use Cases - Squad Discovery: Locate other squads via .squad/manifest.json files, upstream configs, or a central registry, and read their declared capabilities. - Work Delegation Protocol: Create properly labeled cross-squad issues in target repositories using gh issue create, with acceptance criteria and links back to the originating work. - Feedback Loop Tracking: Poll delegated issue status with gh issue view and update the originating squad's orchestration log until completion. - Use Case: A frontend squad needs a Prometheus metrics endpoint added to a service owned by the platform squad. The agent discovers the platform squad's manifest, verifies it accepts issues, and delegates the task with full context and acceptance criteria. ## Quick Start Ask the agent to discover available squads and delegate a task to the appropriate squad using the cross-squad handoff protocol.

Frequently Asked Questions about cross-squad

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

FAQPage Schema
How do I delegate work to another squad's repository?

Check the target squad's manifest to confirm it accepts issues, then create an issue in its repository using gh issue create with a [cross-squad] title prefix, the squad's configured label, acceptance criteria, and a link back to the originating issue.

How does squad discovery work across repositories?

Discovery reads .squad/manifest.json files from well-known paths in known org repos, checks squads listed in .squad/upstream.json, or consults a central squad-registry.json. Each manifest declares the squad's name, capabilities, contact repo, and accepted work types.

What context should I share when delegating cross-squad work?

Share only the capability list, decisions that affect the target squad, and a concise handoff description. Never share internal team state, full decision archives, credentials, tokens, or internal URLs in cross-squad issues.

How do I track delegated work completion?

Record the cross-squad issue URL in the originating squad's orchestration log, then poll the target issue status with gh issue view. Update the originating issue on status changes and close the feedback loop when the delegated work merges.

What are the limitations of cross-squad delegation?

Delegation is asynchronous and issue-based, so it does not suit urgent synchronous work. Avoid open-ended requests without acceptance criteria or timeouts, and watch for circular delegation chains where squads delegate back and forth.