cross-squad

Coordinate cross-squad work across multiple repositories using manifest-based discovery.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-squad coordination is often brittle and slow, leading to duplicated effort and misaligned work across multiple squads. This skill teaches agents how to discover, share context, and hand off work across repository boundaries without creating tight coupling.

Core Features & Use Cases

  • Manifest-based discovery: Agents locate squads via well-known paths, upstream lists, and a central registry to enable cross-squad visibility.
  • Context sharing and safe handoffs: Share only the necessary decisions and context to prevent leakage of internal details.
  • Handoff protocol and tracking: Create and track cross-squad tasks, updating stakeholders automatically.

Quick Start

Delegate a task to a target squad using the cross-squad workflow and manifest-based discovery.

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?

You can coordinate cross-squad work across multiple repositories by applying manifest-based discovery to locate squads and using a handoff protocol to track tasks. This enables safe context sharing without tight coupling.

What is manifest-based squad discovery and how does it work?

Manifest-based squad discovery is a mechanism where agents locate target squads via well-known paths, upstream lists, and a central registry. It provides cross-squad visibility by standardizing how teams are found across repository boundaries.

How do I share context safely during cross-squad handoffs?

You share context safely during cross-squad handoffs by transferring only the necessary decisions and context to the target squad. This prevents leakage of internal details while maintaining alignment across domains.

When do I need a cross-squad handoff protocol for multi-repo workflows?

You need a cross-squad handoff protocol when tasks span multiple squads or domains requiring coordinated work. It allows you to create, track, and update cross-squad tasks while automatically notifying stakeholders of progress.

Can I track cross-squad task progress automatically across repository boundaries?

Yes, you can track cross-squad task progress automatically by implementing the handoff protocol and progress tracking features. This allows stakeholders to receive automatic updates as work moves between squads.

What is the best way to avoid duplicated effort when coordinating multiple squads?

The best way to avoid duplicated effort is to use manifest-based discovery and safe context sharing to coordinate cross-squad work. This prevents misaligned work and duplicated effort by establishing clear visibility and handoff protocols.