What problem does it solve? Setting up a multi-agent team structure from scratch is error-prone: roster files, casting state, agent folders, and Git merge configuration all need to be created consistently. This Skill guides the coordinator through a two-phase flow that proposes a team roster, waits for explicit user confirmation, and then creates the complete .squad/ directory structure. ## Core Features & Use Cases - Two-phase initialization: Phase 1 proposes a cast-named team roster and confirms it via an ask_user selectable menu; Phase 2 creates directories, casting state files, and seeded agent histories only after confirmation. - Casting and naming rules: Selects character names from a universe, keeps Scribe and Ralph exempt from casting, and initializes casting/policy.json, registry.json, and history.json. - Workflow-safe conventions: Enforces the exact ## Members header in team.md required by GitHub label automation, and configures union merge drivers in .gitattributes for append-only squad files. - Use Case: A developer starts a new TypeScript CLI project with no .squad/team.md; the coordinator asks what they are building, proposes a five-agent cast, and on confirmation scaffolds the full team structure with seeded context. ## Quick Start Ask the coordinator to initialize a new squad team for your project and confirm the proposed roster when prompted.
