skills.rest
Leep-GH
Leep-GHCOMMUNITY
Explore all skills by this author →
GitHub

cross-squad

Coordinate cross-squad work handoffs using manifest-based discovery and issue tracking.

Updated Apr 16, 2026
Search Tags:#delegation#handoff#manifest#squad#context-sharing#cross-squad
One-click install
npx skills add https://github.com/Leep-GH/Lee-s-squad --skill cross-squad-leep-gh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cross-squad
Source: https://github.com/Leep-GH/Lee-s-squad/tree/main/packages/squad-cli/templates/skills/cross-squad
Command: npx skills add https://github.com/Leep-GH/Lee-s-squad --skill cross-squad-leep-gh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When an organization runs multiple Squad instances, those squads need to discover each other, share context, and hand off work across repository boundaries. Cross-squad orchestration helps coordinate these activities without creating tight coupling.

Core Features & Use Cases

  • Discovery via Manifest: Squads publish manifests and use well-known paths, upstream configs, or a central registry to locate peers.
  • Context Sharing: Share only the necessary decisions and context when delegating work to another squad.
  • Work Handoff Protocol: Check target manifest, create an issue, track progress, and poll for completion to close the loop.
  • Real-World Scenarios: Coordinating platform, frontend, and data squads on a feature spanning multiple repos and teams.

Quick Start

Describe the task and delegate it to the appropriate squad using the cross-squad 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 handoffs across multiple squads in different repositories?▼

Coordinate cross-squad work handoffs by checking the target squad manifest, creating an issue, tracking progress, and polling for completion to close the feedback loop across repository boundaries.

What is manifest-based discovery for multi-squad collaboration?▼

Manifest-based discovery allows squads to publish manifests to well-known paths, upstream configs, or a central registry so peer squads can locate each other without tight coupling.

How do I share context safely when delegating work to another squad?▼

Share context safely by transferring only the necessary decisions and context relevant to the specific delegated task, preventing tight coupling between the collaborating squads.

Can I use this cross-squad protocol to coordinate platform, frontend, and data teams?▼

Yes, the cross-squad protocol applies to multi-repo features requiring platform, frontend, data, or infrastructure squads to collaborate on a single initiative without tight coupling.

What is the standard workflow for a cross-squad work delegation?▼

The standard cross-squad delegation workflow involves checking the target manifest, creating an issue in the peer squad, tracking progress, and polling for completion to close the feedback loop.

Related Skills

Explore More Software Engineering Skills→
mpauloskympaulosky

cross-squad

Coordinate cross-squad work by discovering manifests and delegating issues or PRs.

Community
Intermediate
dotnetdotnet
209

cross-squad

Discover squad ownership via manifests and delegate work with labeled tracking issues.

Official
Intermediate
jonnymuirjonnymuir
1

cross-squad

Coordinate cross-squad task delegation via manifest-based discovery and issue-tracking protocols.

Community
Intermediate
CommunityToolkitCommunityToolkit
619

cross-squad

Discover squad capabilities and delegate work across Squad instances.

Official
Advanced