cross-squad

Discover squad ownership via manifests and delegate work with labeled tracking issues.

209|27|Updated Mar 10, 2026

Search Tags:#orchestration #GitHub issues #cross-squad #handoff context #squad discovery #work delegation #manifest registry

Ready to run

npx skills add https://github.com/dotnet/maui-labs --skill cross-squad-dotnet

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cross-squad
Source: https://github.com/dotnet/maui-labs/tree/main/src/Comet/.copilot/skills/cross-squad
Command: npx skills add https://github.com/dotnet/maui-labs --skill cross-squad-dotnet

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh issue create, gh issue view, squad discover, squad delegate.

What problem does it solve?

Cross-squad coordination becomes chaotic when teams need to share context and hand off work across repositories without tight coupling or duplicated effort.

Core Features & Use Cases

Discovery via Manifest: Locates squads and their capabilities using .squad/manifest.json, upstream config, or a central registry.
Context Sharing with Guardrails: Selects only the relevant capability list and decision excerpts needed by the target squad.
Work Handoff Protocol: Creates an appropriately labeled cross-squad issue, tracks it, and runs a feedback loop until completion.

Quick Start

Delegate a cross-repository task by having your agent discover the target squad’s manifest, create a labeled handoff issue in the correct repository, and then poll for status updates until the work is completed.

Frequently Asked Questions about cross-squad

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

FAQPage Schema

How do I delegate cross-repository work to another squad without tight coupling?▼

Cross-repository work delegation uses manifest-based discovery to locate the target squad and creates a labeled tracking issue in their repository. This enables work handoff without tight coupling by sharing only the minimal context required.

How do I find which squad owns a specific capability for an infrastructure request?▼

Squad discovery for infrastructure requests is handled by locating squads and their capabilities using `.squad/manifest.json`, upstream configuration, or a central manifest registry. This identifies the correct owner before routing the request.

What is the best way to track cross-squad issues after handing off an architectural decision?▼

Tracking cross-squad issues involves creating an appropriately labeled GitHub issue in the target repository and performing periodic polling. This feedback loop runs until the architectural decision implementation is completed.

Do I need a manifest file to route features spanning multiple repositories?▼

A manifest file like `.squad/manifest.json` or a central registry is required to route features spanning multiple repositories. It provides the squad discovery mechanism needed to identify the correct repository and owner for the work.

What context should I share when handing off work to another squad?▼

When handing off work to another squad, you should share only the relevant capability list and decision excerpts needed by the target squad. This minimal context handoff prevents duplicated effort and maintains guardrails.

Can I use GitHub issues for cross-squad coordination across different repositories?▼

GitHub issues facilitate cross-squad coordination by serving as the tracking mechanism for delegated work. A labeled issue is created in the target repository, and its status is polled until the feedback loop completes.