cross-squad

Coordinate cross-squad work across multiple Squad instances via manifests and handoffs.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/CarlosSardo/nats-poc-simulator --skill cross-squad
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cross-squad
Source: https://github.com/CarlosSardo/nats-poc-simulator/tree/main/.copilot/skills/cross-squad
Command: npx skills add https://github.com/CarlosSardo/nats-poc-simulator --skill cross-squad

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating work across multiple Squad instances to avoid miscommunication and ensure smooth handoffs across repositories.

Core Features & Use Cases

  • Discovery & onboarding: Squads publish a well-known manifest so others can locate capabilities.
  • Context Sharing & Delegation: Share only what's needed and delegate work to the appropriate squad.
  • Handoff Protocol & Tracking: Create issues, link back, and monitor progress across squads.

Quick Start

Interrogate known squads with a discovery command and delegate cross-squad work when a task spans repositories.

Frequently Asked Questions about cross-squad

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

FAQPage Schema
How do I coordinate cross-squad work across multiple repositories?

Cross-squad coordination across multiple repositories is handled through manifest-based discovery, contextual handoff, and a structured delegation workflow to share context and track progress across squads.

What is manifest-based discovery for multi-repo workflows?

Manifest-based discovery is a mechanism where squads publish a well-known manifest so others can locate their capabilities, enabling smooth onboarding and contextual delegation across repositories.

How do I delegate tasks and share context with another squad?

You delegate tasks to another squad by sharing only the necessary context and using a structured handoff protocol to create issues, link back to the original repo, and monitor progress.

When do I need a cross-squad handoff protocol?

A cross-squad handoff protocol is needed when a task spans several squads and repositories, requiring shared context and structured delegation to avoid communication silos and misalignment.

Can I track cross-squad issue progress across different repositories?

Yes, cross-squad issue tracking is supported through a handoff protocol that links created issues back to the originating squad and monitors progress across the involved repositories.

What's the best way to avoid silos when working across multiple squads?

The best way to avoid silos across multiple squads is to use manifest-based discovery to locate capabilities and apply a structured delegation workflow for contextual handoffs and progress tracking.