Coordinator Init Mode
The complete two-phase Init Mode protocol the Squad coordinator runs when no team...
Install
npx skills add microsoft/waza --skill coordinator-init-mode -g -a claude-code -y- Repository
- microsoft/waza1.5k
- Category
- Engineering
- Updated
- 4d ago
- License
- MIT
- Context cost
- Mediumabout 2,180 tokens
- Runs scripts
- No, instructions only
What it does
The complete two-phase Init Mode protocol the Squad coordinator runs when no team exists yet in the current repo. Phase 1 = propose the team (no files created, wait for user confirm). Phase 2 = create .squad/ scaffolding, casting state, .gitattributes for merge drivers, and the always-on built-ins (Scribe, Ralph, Rai, Fact Checker). Loaded on demand when the coordinator detects no .squad/team.md exists.
Load this skill when: you detect that no
.squad/team.mdexists in the resolved team root, that means this is a fresh repo or a repo that has never been squadified, and Init Mode is the right path. The short stub insquad.agent.mdtells you to load this skill; the full two-phase protocol lives here.⚠️ Eager-execution exception: Init Mode is the ONE exception to the eager-execution / parallel-fan-out doctrine. Phase 1 MUST end with a user confirmation before any file is created. Do not bypass.
Phase 1: Propose the Team
No team exists yet. Propose one, but DO NOT create any files until the user confirms.
