cross-squad

Coordinate cross-squad work via manifest discovery and issue tracking.

7|Updated Oct 24, 2020
One-click install
npx skills add https://github.com/snow-jallen/HomeSpeaker --skill cross-squad-snow-jallen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cross-squad
Source: https://github.com/snow-jallen/HomeSpeaker/tree/main/.copilot/skills/cross-squad
Command: npx skills add https://github.com/snow-jallen/HomeSpeaker --skill cross-squad-snow-jallen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating work across multiple Squad instances requires discovery, safe context sharing, and reliable handoffs across repository boundaries to prevent fragmentation and delays.

Core Features & Use Cases

  • Discovery via .squad manifests, upstream references, and optional registries to locate capable squads
  • Context sharing during delegation to minimize exposed decisions and protect sensitive data
  • Work handoff protocol including issue creation, status tracking, and cross-squad feedback
  • Real-world use: coordinating UI and backend tasks spanning multiple repos

Quick Start

Publish your squad manifest and use the cross-squad tools to delegate a task to another squad.

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 and repositories?

You can coordinate cross-squad work by publishing a squad manifest to locate capable squads, sharing context during delegation, and using a handoff protocol with issue creation and status tracking to prevent fragmentation.

What is a .squad manifest and how does it help with cross-squad coordination?

A .squad manifest is a discovery file used to locate capable squads within an organization. It enables cross-squad coordination by allowing upstream references and optional registries to identify available teams for task delegation.

How do I delegate tasks to another squad without exposing sensitive decisions?

You delegate tasks safely by using controlled context sharing during the delegation process, which minimizes exposed decisions and protects sensitive data while transferring work across squad boundaries.

Can I use cross-squad coordination for multi-repo workflows spanning platform, frontend, data, and infra?

Yes, cross-squad coordination supports multi-repo workflows spanning platform, frontend, data, and infra, allowing you to seamlessly coordinate tasks like UI and backend dependencies across different repository boundaries.

What's the best way to track cross-squad task status after handing off work?

The best way to track cross-squad task status is by using a work handoff protocol that includes issue creation, status tracking, and cross-squad feedback to maintain visibility after delegation.

Why does cross-squad work often face fragmentation and delays, and how can I prevent it?

Cross-squad work faces fragmentation and delays due to disconnected repository boundaries. You can prevent this by using manifest discovery, protected context sharing, and a structured handoff protocol with issue tracking.