cross-squad

Coordinate inter-team task delegation and squad discovery via manifest files and issue-tracking protocols.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/Quintenps/contactswap-agents --skill cross-squad-quintenps
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cross-squad
Source: https://github.com/Quintenps/contactswap-agents/tree/main/.copilot/skills/cross-squad
Command: npx skills add https://github.com/Quintenps/contactswap-agents --skill cross-squad-quintenps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the friction of cross-team collaboration by providing a standardized protocol for discovering squad capabilities and delegating tasks without creating tight coupling or architectural bottlenecks.

Core Features & Use Cases

  • Squad Discovery: Automatically identify available squads, their specific capabilities, and contact points via manifest files.
  • Standardized Delegation: Create and track work items in external repositories using a consistent issue-based communication protocol.
  • Use Case: When a frontend feature requires a new backend API endpoint, use this skill to discover the backend squad's manifest and delegate the task with clear acceptance criteria and tracking.

Quick Start

Use the cross-squad skill to delegate the task of adding a new Prometheus metrics endpoint to the platform-squad.

Frequently Asked Questions about cross-squad

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

FAQPage Schema
How do I delegate tasks to other teams in a multi-repository environment?▼

You can delegate tasks to other teams by using manifest-based communication patterns to discover squad capabilities and creating standardized, traceable work items in external repositories. This ensures decoupled cross-team task delegation without architectural bottlenecks.

What is a squad manifest file and how does cross-team collaboration work?▼

A squad manifest file is a standardized protocol artifact that identifies available squads, their specific capabilities, and contact points. Cross-team collaboration works by leveraging these manifests to coordinate inter-team task discovery and issue-based delegation across team boundaries.

Do I need manifest files in every repository to coordinate cross-functional work?▼

Yes, you need manifest files in target repositories to enable squad discovery and standardized issue-tracking. Adherence to these manifest-based communication patterns is required to ensure decoupled and traceable work handoffs across multi-repository environments.

When should I not use manifest-based delegation for inter-team task orchestration?▼

Manifest-based delegation is not suitable for single-repository environments or features that do not require cross-functional support. It should only be applied to multi-repository environments where architectural decisions necessitate standardized, decoupled work handoffs.

What's the best way to track work items handed off to external squads?▼

The best way to track work items handed off to external squads is by using a standardized issue-based communication protocol. This creates clear acceptance criteria and traceable tracking for delegated tasks in external repositories without tight coupling.