What problem does it solve?
When a repository has never been set up with a Squad agent team, the coordinator needs a safe, structured way to propose a team roster and then create all the required .squad/ scaffolding without prematurely writing files before the user confirms.
Core Features & Use Cases
- Two-phase init protocol: Phase 1 proposes a cast of 4-5 domain agents plus the four always-on built-ins (Scribe, Ralph, Rai, Fact Checker) and waits for explicit user confirmation; Phase 2 creates the .squad/ directory structure only after approval.
- Casting and naming: Runs the casting algorithm to select a character universe, allocate persistent agent names, and seed casting state (policy.json, registry.json, history.json).
- Scaffolding and merge safety: Creates team.md with the mandatory
## Members header used by GitHub workflow label automation, seeds agent charters and history files, and configures .gitattributes union merge drivers for append-only squad state files.
- Use Case: A developer opens a fresh repository with the Squad coordinator; the skill detects the missing .squad/team.md, proposes a themed team roster for confirmation, then scaffolds the full team structure and offers optional PRD, GitHub issues, and Copilot agent onboarding.
Quick Start
Ask the coordinator to set up a new Squad team in this repository and confirm the proposed roster when prompted.
