cross-squad

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

Updated Mar 18, 2022
One-click install
npx skills add https://github.com/mpaulosky/dotfiles --skill cross-squad-mpaulosky
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cross-squad
Source: https://github.com/mpaulosky/dotfiles/tree/main/.copilot/skills/cross-squad
Command: npx skills add https://github.com/mpaulosky/dotfiles --skill cross-squad-mpaulosky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When an organization runs multiple Squad instances, teams need a reliable, low-coupling way to discover capabilities, share only relevant context, and hand off work across repository boundaries without modifying another squad's internal files.

Core Features & Use Cases

  • Manifest-based discovery: Locate squads and their capabilities via .squad/manifest.json, upstream lists, or a central registry.
  • Safe context sharing: Provide concise handoff details and acceptance criteria while excluding secrets and internal state.
  • Issue-based delegation & tracking: Create issues or PRs in target repos with a cross-squad label, record links back to the origin, and poll status until completion.
  • Guardrails & anti-patterns: Enforce non-destructive communication (issues/PRs only), avoid tight coupling, and prevent circular delegation.

Quick Start

Delegate a task to another squad by creating an issue in the target repository that includes context, acceptance criteria, a cross-squad label, and a link back to the originating work.

Frequently Asked Questions about cross-squad

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

FAQPage Schema
How do I delegate work across multiple GitHub repositories in different squads?

Cross-squad issue delegation works by discovering squad manifests (.squad/manifest.json) and creating labeled issues or PRs in target repositories. This enforces non-destructive communication and tracks cross-repository handoffs without modifying another squad's internal files.

What is a squad manifest and how does it enable cross-team discovery?

A squad manifest (.squad/manifest.json) enables manifest-based discovery by listing squad capabilities. It allows your organization to locate squads via upstream lists or a central registry, facilitating safe context sharing and cross-repository handoffs.

How do I track the status of a delegated issue across squads?

You track cross-squad work by recording links back to the origin and polling the status of delegated issues or PRs until completion. This issue-based tracking approach maintains low coupling between squads while monitoring cross-repository handoffs.

Can I share internal state and secrets when handing off issues to another squad?

No, you must exclude secrets and internal state when handing off issues to another squad. Cross-squad delegation enforces safe context sharing by providing only concise handoff details and acceptance criteria via issues or PRs.

What permissions do I need to create cross-squad issues in target repositories?

You need permission to create issues or PRs in target repositories and readable .squad/manifest.json entries for manifest-based discovery. These permissions enable safe context sharing and issue-based delegation across squad boundaries.

How do I prevent circular delegation when orchestrating cross-squad work?

The Skill enforces guardrails and anti-patterns to prevent circular delegation by restricting communication to non-destructive issues or PRs. This avoids tight coupling and ensures cross-squad handoffs flow in a single direction across repositories.