cross-squad

Coordinate cross-squad work across repositories using squad manifests and issue-based delegation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-squad coordination across multiple squads helps teams discover, share context, and hand off work without tight coupling, reducing friction when features span repos.

Core Features & Use Cases

  • Discovery via Manifest: squads publish a .squad/manifest.json to expose capabilities and contact info.
  • Context Sharing: hand off only what the target squad needs, avoiding sensitive internal state.
  • Work Handoff Protocol: create cross-squad issues with clear context, acceptance criteria, and traceability.
  • Feedback Loop: track delegation status and surface progress back to the origin.

Quick Start

Define the target squads' manifests and use the discovery and delegation commands to route work across repositories.

Frequently Asked Questions about cross-squad

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

FAQPage Schema
How do I coordinate cross-squad work across multiple repositories?

Cross-squad work across multiple repositories is coordinated by applying a handoff protocol using squad manifests, context sharing, and issue-based delegation to route tasks between teams.

When do I need a handoff protocol for cross-squad coordination?

A handoff protocol is needed when a task spans platform, frontend, or data squads, requires shared infrastructure, or needs work routed across multiple repositories without tight coupling.

How do I set up squad manifests for work discovery and delegation?

Set up squad manifests by having each squad publish a .squad/manifest.json file to expose their capabilities and contact info, enabling discovery and delegation commands to route work.

How does context sharing work when handing off work between squads?

Context sharing provides the target squad only with the necessary context and acceptance criteria, avoiding sensitive internal state exposure while maintaining traceability and feedback loops.

What is the best way to avoid tight coupling when routing work across squads?

The best way to avoid tight coupling is using issue-based delegation with published squad manifests, creating cross-squad issues that track delegation status and surface progress back to the origin.

Can I use cross-squad coordination for tasks spanning frontend and data squads?

Yes, cross-squad coordination applies when tasks span platform, frontend, and data squads or require shared infrastructure, enabling context sharing and work handoffs across these boundaries.