# Coordinator Init Mode

The complete two-phase Init Mode protocol the Squad coordinator runs when no team...

- Repository: https://github.com/microsoft/waza (1496 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-10-31
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add microsoft/waza --skill coordinator-init-mode -g -a claude-code -y`
Codex: `npx skills add microsoft/waza --skill coordinator-init-mode -g -a codex -y`
Cursor: `npx skills add microsoft/waza --skill coordinator-init-mode -g -a cursor -y`
Gemini CLI: `npx skills add microsoft/waza --skill coordinator-init-mode -g -a gemini-cli -y`

## Description

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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

> **Load this skill when:** you detect that no `.squad/team.md` exists 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 in `squad.agent.md` tells 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.**

The rest: https://github.com/microsoft/waza/blob/HEAD/.github/skills/coordinator-init-mode/SKILL.md