cross-squadlisted

## Context When an organization runs multiple Squad instances (e.g., platform-squad, frontend-squad, data-squad), those squads need to discover each other, share context, and hand off work across repository boundaries. This skill teaches agents how to coordinate across squads without creating tight coupling. Cross-squad orchestration applies when: - A task requires capabilities owned by another squad - An architectural decision affects multiple squads - A feature spans multiple repositories with different squads - A squad needs to request infrastructure, tooling, or support from another squad ## Patterns ### Discovery via Manifest Each squad publishes a `.squad/manifest.json` declaring its name, capabilities, and contact information. Squads discover each other through: 1. **Well-known paths**: Check `.squad/manifest.json` in known org repos 2. **Upstream config**: Squads already listed in `.squad/upstream.json` are checked for manifests 3. **Explicit registry**: A central `squad-registry.json` can list all squads in an org ```json { "name": "platform-squad", "version": "1.0.0", "description": "Platform infrastructure team", "capabilities": ["kubernetes", "helm", "monitoring", "ci-cd"], "contact": { "repo": "org/platform", "labels": ["squad:platform"] }, "accepts": ["issues", "prs"], "skills": ["helm-developer", "operator-developer", "pipeline-engineer"] } ``` ### Context Sharing When delegating work, share only what the target squad needs: - **Cap