cross-squad

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.

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.

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.

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.

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.

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.