Route tasks across repositories to squads using manifest-based capability discovery.
npx skills add https://github.com/elbruno/md-to-slides --skill cross-squad-elbruno
Please help me install this Agent Skill. Skill: cross-squad Source: https://github.com/elbruno/md-to-slides/tree/main/.copilot/skills/cross-squad Command: npx skills add https://github.com/elbruno/md-to-slides --skill cross-squad-elbruno
Cross-squad coordination prevents teams from duplicating effort or blocking each other when features span multiple repositories owned by different squads, by providing a safe, standard handoff process.
.squad/manifest.json (and optional upstream/registry listings).Use the cross-squad skill to delegate the work “Add Prometheus metrics endpoint for the auth service” to the platform squad.
High-intent search queries and answers about installing and using this skill.
To delegate tasks across multiple GitHub repositories, this skill routes work to the correct squad using published manifests and creates labeled tracking issues with acceptance criteria in the target repo. It then polls periodically to update status until completion.
Manifest discovery for cross-squad workflow tracking works by reading `.squad/manifest.json` files and optional upstream registries to find which squad owns the required capabilities. This allows safe context handoff without coupling internal states or sharing secrets.
The best way to coordinate platform changes spanning multiple repos is to delegate each piece to the appropriate squad based on declared capabilities. The skill creates labeled issues for tracking and polls them to close the loop as work progresses.
Yes, you need a `.squad/manifest.json` file to enable cross-repository orchestration and task handoff. The manifest provides the capability contracts required to discover the correct target squad and route the delegated work safely.
No, you should not share internal state or secrets during repo handoff. This skill enforces strict boundaries by delegating only capability lists, relevant architectural decisions, and concise handoff context to the target squad.
Issue-based work handoff prevents teams from duplicating effort or blocking each other by providing a standard tracking protocol. It creates labeled GitHub issues in the target repository and polls status updates to ensure work completion without coupling repos.
nicolehaugenDiscover Squad capabilities and delegate tasks across Squad instances.
Leep-GHConvert retro action items into GitHub Issues at round start.
evanharmon1Validate GitHub PR closing keywords against issue acceptance criteria.
sachinnair90Coordinate cross-squad handoffs and shared context across repository boundaries.