cross-squad

To coordinate work across multiple GitHub repositories, you can use a manifest-based discovery and issue-based delegation protocol. This allows independent squad teams to share context and hand off tasks without tight coupling by creating well-structured cross-repo issues.

Manifest-based discovery is finding squads and their capabilities via a published .squad/manifest.json file or a central registry. It enables teams to locate the right repository for delegating features that span multiple independent squad instances.

You delegate a feature request by creating a cross-squad issue in the target repository with clear context, acceptance criteria, and labels. This structured issue provides the originating squad a precise way to request work from the receiving team.

Yes, you can track delegated tasks by polling the GitHub issues or using status tracking. This updates the origin tickets with progress and closes the feedback loop to ensure accountability across the squads until the pull request is merged.

You need a cross-squad orchestration protocol when a feature spans multiple repositories or requires capabilities owned by different squads. It resolves the friction of handing off work between independently owned squad repositories.

The best way to hand off tasks is discovering the platform squad's manifest, creating a cross-squad GitHub issue with specific acceptance criteria, and tracking the resulting pull request. This lightweight protocol ensures clear delegation without tight coupling.