cross-squad

Name: cross-squad
Availability: InStock
Author: waynewalterberry

Coordinate cross-squad work across multiple repositories via manifest discovery and delegation.

Updated Mar 19, 2026

Search Tags:#delegation #handoff #manifest #cross-repo #squad #coordinate

Ready to run

npx skills add https://github.com/WayneWalterBerry/MMO --skill cross-squad-waynewalterberry

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cross-squad
Source: https://github.com/WayneWalterBerry/MMO/tree/main/.copilot/skills/cross-squad
Command: npx skills add https://github.com/WayneWalterBerry/MMO --skill cross-squad-waynewalterberry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-squad orchestration coordinates work between multiple Squad instances, enabling discovery, context sharing, and handoffs across repository boundaries to reduce coordination debt.

Core Features & Use Cases

Discovery via manifest: squads publish a .squad/manifest.json and become discoverable.
Context sharing: share only what's needed for delegation, preserving privacy and reducing coupling.
Work handoff protocol: create issues/PRs in target repos with clear context and acceptance criteria; track progress and rejoin outcomes.
Use Case: when a feature spans platform-squad and frontend-squad, coordinate tasks and ensure alignment through delegated work items.

Quick Start

Publish a manifest for your squad and delegate work to another squad using the squad delegate command.

Frequently Asked Questions about cross-squad

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

FAQPage Schema

How do I coordinate work across multiple squads in different repositories?▼

Cross-squad coordination orchestrates work between multiple squads by using manifest discovery, context sharing, and a work handoff protocol to track delegated tasks across repository boundaries.

What is a manifest and how does it work for cross-repo delegation?▼

A manifest is a published .squad/manifest.json file that makes a squad discoverable, enabling other squads to find its capabilities and delegate work items with shared context.

How do I hand off tasks to another squad without creating tight coupling?▼

You hand off tasks by creating issues or PRs in target repositories with clear context and acceptance criteria, sharing only the necessary information to preserve privacy and reduce coordination debt.

When do I need cross-squad orchestration for an architectural change?▼

Cross-squad orchestration is needed for multi-squad initiatives, architectural changes, or tasks requiring other squads' capabilities, such as a feature spanning platform and frontend squads.

Can I track progress and outcomes after delegating work to another squad?▼

Yes, the delegation protocol includes tracked feedback loops that monitor progress and rejoin outcomes to ensure completion of the delegated work items across squads.

What are the limitations of cross-squad orchestration for multi-squad initiatives?▼

Orchestration requires each squad to publish a manifest for discovery and relies on a structured handoff protocol, which may not suit loosely organized teams lacking clear ownership boundaries.