What problem does it solve? When an organization runs multiple Squad instances (platform-squad, frontend-squad, data-squad), agents need a reliable way to discover peer squads, share context, and delegate work across repository boundaries without creating tight coupling or confusing the product term "squad" with casual ad-hoc agent fan-out. ## Core Features & Use Cases - Squad Discovery: Find peer squads via .squad/manifest.json, squad registry, and squad upstream mechanisms, with optional inheritance of skills and decisions. - Work Delegation: Hand off tasks to another squad using squad delegate or GitHub issues with cross-squad labels, acceptance criteria, and status tracking. - Disambiguation Guidance: Distinguish real Squad installs from ad-hoc task agent fan-out, and prompt the user with ask_user when intent is ambiguous. - Use Case: A coordinator receives "delegate the Prometheus metrics work to the platform squad" — it discovers the peer via squad registry list, verifies the manifest accepts issues, creates a labeled GitHub issue in the target repo, and polls for completion. ## Quick Start Ask the agent to discover available squads and delegate a specific task to the appropriate peer squad using the squad registry.
