What problem does it solve? Setting up a multi-agent AI team from scratch requires consistent structure, naming, and state files; this Skill guides a two-phase flow that proposes a cast roster and only creates the .squad/ directory after explicit user confirmation. ## Core Features & Use Cases - Two-Phase Initialization: Phase 1 proposes a cast team roster and waits for confirmation via an ask_user menu; Phase 2 creates the .squad/ structure, casting state, and seeded agent histories. - Casting & Naming: Selects character names from a universe (custom universes preferred) with Scribe and Ralph exempt from casting. - Workflow-Safe Structure: Enforces the exact ## Members header in team.md required by GitHub label-routing workflows, and configures union merge drivers in .gitattributes for append-only files. - Use Case: A developer starting a new TypeScript CLI project triggers Init Mode, confirms a proposed team of Lead, Frontend, Backend, and Tester agents, and gets a fully seeded .squad/ directory ready for task routing. ## Quick Start Ask the coordinator to set up a new squad team for your project and confirm the proposed roster when prompted.