cross-squad

Coordinate cross-squad work across repositories using manifests and handoff protocols.

Updated Jan 5, 2026
One-click install
npx skills add https://github.com/Golnaz89/golnaz89.github.io --skill cross-squad-golnaz89
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cross-squad
Source: https://github.com/Golnaz89/golnaz89.github.io/tree/main/.copilot/skills/cross-squad
Command: npx skills add https://github.com/Golnaz89/golnaz89.github.io --skill cross-squad-golnaz89

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating work across multiple Squad instances can create friction if context isn't shared and handoffs are not clearly defined. This Skill provides a structured approach to discovery, context sharing, and controlled delegation across repository boundaries to keep squads loosely coupled.

Core Features & Use Cases

  • Discovery via Manifest: Squads publish a .squad/manifest.json declaring name, capabilities, and contact information to enable automatic cross-squad discovery.
  • Context Sharing: When delegating work, share only what the target squad needs, including capability lists, relevant decisions, and a concise handoff description; avoid exposing internal state or secrets.
  • Work Handoff Protocol: Verify manifest acceptance, create an issue in the target repository with a clear title and cross-squad label, and track progress until completion.
  • Feedback Loop: Poll the delegated work status and update the originating context to close the loop when the work merges.

Quick Start

Publish a squad manifest, share decisions, and delegate work across repositories using the cross-squad handoff protocol.

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 repositories handled by different squads?

Cross-squad coordination uses a manifest-based discovery process to identify target capabilities, followed by a formal handoff protocol that creates tracked issues in target repositories to reduce friction.

What is a squad manifest and how does it enable cross-squad discovery?

A squad manifest is a `.squad/manifest.json` file that declares a squad's name, capabilities, and contact information. It enables automatic cross-squad discovery by allowing other squads to programmatically find and delegate work to the relevant team.

How do I hand off tasks to another squad without exposing internal state or secrets?

When delegating work via the handoff protocol, share only what the target squad needs, including capability lists, relevant decisions, and a concise handoff description, thereby avoiding exposure of internal state or secrets.

When should I use a formal cross-squad handoff protocol for my project?

You should use a cross-squad handoff protocol when a task spans multiple squads, requires capabilities from a different squad, or needs shared decisions across repositories to keep loosely coupled teams aligned.

How do I track the status of delegated work after a cross-squad handoff?

You track delegated work by polling the status of the created issue in the target repository. This feedback loop updates the originating context and closes the loop when the work merges.

Does cross-squad coordination require any specific dependencies or components?

No dependencies or components are required. The cross-squad coordination relies on publishing a `.squad/manifest.json` file and implementing a formal handoff protocol with issue creation and status tracking across repositories.