What problem does it solve? Setting up a multi-agent team structure manually is error-prone and inconsistent. This Skill guides the coordinator through a two-phase initialization flow that proposes a cast of named agents, waits for explicit user confirmation, and then creates the complete .squad directory structure with correct conventions. ## Core Features & Use Cases - Two-Phase Team Setup: Phase 1 proposes a team roster using a casting algorithm with themed universes; Phase 2 creates directories, casting state files, and seeded agent histories only after confirmation. - Convention Enforcement: Ensures team.md uses the exact ## Members header required by GitHub workflow label automation, and configures union merge drivers in .gitattributes for conflict-free append-only logs. - Privacy Guardrails: Reads only git config user.name and explicitly forbids storing user email addresses in committed files. - Use Case: A developer starts a new TypeScript CLI project with no .squad/team.md. The coordinator detects the missing team, casts agents from a themed universe, confirms the roster via a selectable menu, then scaffolds the full team structure with seeded context. ## Quick Start Ask the coordinator to set up a new squad team for your project and confirm the proposed roster when prompted.