cross-squad

Coordinate cross-squad work via manifest discovery and delegated issue handoffs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating work across multiple Squad instances to reduce coupling and streamline handoffs between teams.

Core Features & Use Cases

  • Discovery via manifest: squads publish a .squad/manifest.json to enable lightweight discovery and capability awareness.
  • Context sharing and handoff: when delegating work, share only the necessary decisions and context to minimize coupling.
  • Work handoff protocol: create issues/PRs with clear acceptance criteria and track progress across squads.

Quick Start

Ask the cross-squad agent to delegate a task to a partner squad with clear context.

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?

To coordinate cross-squad work across different repositories, this Skill uses a manifest-based discovery protocol combined with delegated issue workflows to share context and track handoffs. Squads publish a manifest file to enable capability awareness and streamline collaboration.

What is a manifest-based discovery protocol for cross-squad collaboration?

A manifest-based discovery protocol for cross-squad collaboration works by having each squad publish a .squad/manifest.json file. This enables lightweight discovery and capability awareness so other squads can identify partners for architecture decisions or feature delivery.

How do I delegate tasks to another squad without creating tight coupling?

To delegate tasks without tight coupling, share only the necessary decisions and context required for the specific work. This Skill creates issues or PRs with clear acceptance criteria, ensuring minimal dependency while tracking progress across squads.

When do I need a formal work handoff protocol for cross-squad feature delivery?

You need a formal work handoff protocol when multiple squads must collaborate on architecture decisions, feature delivery, or infrastructure needs across different repos. It specifies context sharing and delegated issue workflows to reduce coupling and streamline team coordination.

Does cross-squad coordination work for infrastructure changes across different repos?

Yes, cross-squad coordination applies when multiple squads must collaborate on infrastructure needs across different repos. It specifies discovery, context sharing, and handoff protocols to manage delegated issues and track progress for cross-repository architecture or infrastructure changes.

What is the best way to track cross-squad work handoffs and acceptance criteria?

The best way to track cross-squad work handoffs is by creating issues or PRs with clear acceptance criteria. This Skill establishes a work handoff protocol that specifies context sharing and tracks progress across squads to ensure delegated tasks meet agreed standards.