skills.rest
sachinnair90
sachinnair90COMMUNITY
Explore all skills by this author →
GitHub

cross-squad

Coordinate cross-squad handoffs and shared context across repository boundaries.

Updated Apr 3, 2026
Search Tags:#github#delegation#orchestration#handoff#manifests#repositories#cross-squad
One-click install
npx skills add https://github.com/sachinnair90/gitgloss --skill cross-squad-sachinnair90
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cross-squad
Source: https://github.com/sachinnair90/gitgloss/tree/main/.copilot/skills/cross-squad
Command: npx skills add https://github.com/sachinnair90/gitgloss --skill cross-squad-sachinnair90

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams coordinate work that spans multiple squads, so decisions, ownership, and handoffs stay clear across repository boundaries.

Core Features & Use Cases

  • Squad discovery: Find which squad is best suited for a task by checking manifests and capability lists.
  • Context-safe handoffs: Share only the relevant decisions, acceptance criteria, and origin links needed for another squad to act.
  • Work tracking: Create, monitor, and close cross-squad issues while keeping the originating team informed.
  • Use case: A platform team can delegate a monitoring change to an infrastructure squad, then track the issue until the fix is merged.

Quick Start

Ask the assistant to delegate a cross-squad task to the right team and include the target squad, desired outcome, and acceptance criteria.

Frequently Asked Questions about cross-squad

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

FAQPage Schema
How do I delegate GitHub issues across different repositories to another squad?▼

To delegate GitHub issues across repositories, you create a cross-squad handoff that shares only relevant decisions and acceptance criteria. This protocol tracks the delegated issue while keeping the originating team informed until the fix is merged.

What is the best way to discover which squad owns a specific task across repository boundaries?▼

Discovering the right squad for a task involves checking manifests and capability lists to find the best match. This manifest-based discovery ensures architectural alignment by identifying which team is best suited for the specific work.

How do I share context with another team without exposing repository secrets?▼

Sharing context safely means providing only the relevant decisions, acceptance criteria, and origin links needed for another squad to act. This concise context sharing protocol enables work tracking without exposing sensitive repository secrets.

Can I track cross-squad work handoffs for platform and infrastructure teams using GitHub?▼

Yes, you can track cross-squad work handoffs for platform and infrastructure teams using GitHub issue protocols. A platform team can delegate a monitoring change to an infrastructure squad and monitor the cross-squad issue until the fix is merged.

When do I need manifest-based squad discovery for cross-repository tasks?▼

You need manifest-based squad discovery when a task requires architectural alignment or delegation of issues between repositories. It helps identify the correct squad by checking capability lists before initiating a context-safe work handoff.

Related Skills

Explore More Software Engineering Skills→
elbrunoelbruno
2

cross-squad

Route tasks across repositories to squads using manifest-based capability discovery.

Community
Intermediate
psaabpsaab
8

merge-prs

Merge GitHub pull requests and close referenced issues via gh CLI.

Community
Advanced
ToqsickToqsick

github-grayhack-workflow

Automate GitHub issue creation, branch management, pull requests, and documentation updates.

Community
Advanced
chdalychdaly

cross-squad

Coordinate cross-squad work via manifest discovery and delegated issue handoffs.

Community
Advanced