cross-squad

Coordinate cross-squad work using manifest-driven discovery and handoff protocols.

2|1|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/PlagueHO/plagueho.learn --skill cross-squad-plagueho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cross-squad
Source: https://github.com/PlagueHO/plagueho.learn/tree/main/.copilot/skills/cross-squad
Command: npx skills add https://github.com/PlagueHO/plagueho.learn --skill cross-squad-plagueho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating work across multiple Squad instances can lead to fragmentation, duplicate efforts, and handoff confusion. This Skill provides a structured approach to discover, align, and delegate work across squads while preserving context and governance.

Core Features & Use Cases

  • Squad discovery: Publishes and consumes squad manifests to identify capabilities and ownership.
  • Context-safe handoffs: Shares only necessary decisions and criteria when delegating work between squads.
  • Handoff protocol: Generates actionable tasks, tracks progress, and provides feedback loops across repository boundaries.
  • Use Case: When a feature spans platform, frontend, and data squads, this Skill guides orchestration to avoid bottlenecks and miscommunication.

Quick Start

Delegate a cross-squad task to the appropriate squad with a clear objective and acceptance criteria.

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 to prevent handoff confusion?

Coordinating cross-squad work uses a manifest-driven discovery process to identify capabilities and ownership, enforcing context-safe handoffs and a defined protocol to track progress and provide feedback loops across repository boundaries.

What is the best way to delegate tasks across platform, frontend, and data squads?

Delegating cross-squad tasks requires a clear objective and acceptance criteria, using a structured handoff protocol to generate actionable tasks and preserve necessary decisions without duplicating efforts or losing governance.

How does squad discovery work when orchestrating features that span multiple teams?

Squad discovery works by publishing and consuming squad manifests to identify capabilities and ownership, allowing orchestration across platform, frontend, and data squads to avoid bottlenecks and miscommunication.

Can I share context safely between squads without exposing unnecessary information?

Sharing context safely between squads involves a prudent policy that transmits only necessary decisions and criteria when delegating work, preserving governance while enabling actionable cross-squad task execution.

Do I need a specific manifest format to enable cross-squad collaboration?

Cross-squad collaboration requires a lightweight manifest-driven approach to publish and consume squad capabilities, but the metadata does not specify a strictly enforced file format or external dependencies.

Why does cross-squad task delegation require a feedback loop?

Cross-squad task delegation requires a feedback loop to track progress across repository boundaries and provide structured updates, ensuring the receiving squad meets the original objective and acceptance criteria.