coordinator-init-mode
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.
microsoft · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add microsoft/waza --skill coordinator-init-mode技能说明
name: "coordinator-init-mode" 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." allowedTools: [] confidence: high domain: squad-internals source: "Extracted from squad.agent.md (bradygaster/squad#1308), with Waza project overrides for paired casting initialization and governance-aligned reviewer seeding."
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.
- Identify the user. Run
git config user.nameto learn who you're working with. Use their name in conversation (e.g., "Hey {user}, what are you building?"). Store their name (NOT email) inteam.mdunder Project Context. Never read or storegit config user.email— email addresses are PII and must not be written to committed files. - Ask: "What are you building? (language, stack, what it does)"
- Cast the team. Before proposing names, run the Casting & Persistent Naming algorithm (see the canonical Casting reference at
.squad/templates/casting-reference.md):- Determine team size: pick 4–5 cast (user-domain) agents, then add the 4 always-on built-ins (Scribe + Ralph + Rai + Fact Checker — see their dedicated sections in
squad.agent.md). A typical fresh squad has 8–9 total roster entries, not 4–5. - Determine assignment shape from the user's project description.
- Derive resonance signals from the session and repo context.
- Select a universe. Allocate character names from that universe.
- Scribe is always "Scribe" — exempt from casting.
- Ralph is always "Ralph" — exempt from casting.
- Rai is always "Rai" — exempt from casting.
- Fact Checker is always "Fact Checker" — exempt from casting (same pattern as Scribe / Ralph / Rai).
- Determine team size: pick 4–5 cast (user-domain) agents, then add the 4 always-on built-ins (Scribe + Ralph + Rai + Fact Checker — see their dedicated sections in
- Propose the team with their cast names. Example (names will vary per cast):
🏗️ {CastName1} — Lead Scope, decisions, code review
⚛️ {CastName2} — Frontend Dev React, UI, components
🔧 {CastName3} — Backend Dev APIs, database, services
🧪 {CastName4} — Tester Tests, quality, edge cases
📋 Scribe — (silent) Memory, decisions, session logs
🔄 Ralph — (monitor) Work queue, backlog, keep-alive
🛡️ Rai — (background) RAI awareness, content safety
🔍 Fact Checker — (verifier) Verification + Devil's Advocate
-
Use the
ask_usertool to confirm the roster. Provide choices so the user sees a selectable menu.The
questionmust be self-contained because the client may render the blocking input request without the assistant text that preceded it.The
questionmust reuse every roster line from the exact proposal emitted in step 4, in the same order. Do not regenerate, summarize, truncate, omit, or replace any roster row with an ellipsis. Every proposed member must appear with their emoji, cast name, role, and concise responsibility/scope — including all four always-on built-ins (Scribe, Ralph, Rai, Fact Checker).Shape:
Confirm this team (universe: {ActualUniverse}): {Every roster line from step 4, copied in full and in order} Look right?Never use a bare "Look right?" question and never rely on preceding assistant output to identify the team being confirmed.
- choices:
["Yes, hire this team", "Add someone", "Change a role"]
- choices:
⚠️ STOP. Your response ENDS here. Do NOT proceed to Phase 2. Do NOT create any files or directories. Wait for the user's reply.
Phase 2: Create the Team
Trigger: The user replied to Phase 1 with confirmation ("yes", "looks good", or similar affirmative), OR the user's reply to Phase 1 is a task (treat as implicit "yes").
If the user said "add someone" or "change a role," go back to Phase 1 step 3 and re-propose. Do NOT enter Phase 2 until the user confirms.
- Create the
.squad/directory structure (see.squad/templates/for format guides or use the standard structure:team.md,routing.md,ceremonies.md,decisions.md,decisions/inbox/,casting/,agents/,orchestration-log/,skills/,log/,rai/).
Casting state initialization — Waza project repair: Begin with a genuinely empty new target. Use .squad/casting-transactions.md's actual locked SDK writer to initialize schema-v1 registry/history and their commit manifest together, including complete provenance and the first assignment snapshot; only then initialize policy config exclusively from approved defaults. Do not create either casting JSON file independently or copy legacy examples into live state. On non-local backends, require an equivalent atomic operation or stop; generic per-file state writes are not sufficient.
Initialization requires a genuinely empty new target. The SDK prepares/validates existing files before the callback, so it cannot normalize v0.10 files left in place. Known frozen v0.10 state requires the guide's approved, quiesced archive-and-initialize procedure with disclosed downtime and continuity limits; never infer legacy status from a managed-pair validation failure.
Seeding: Create initial history.md context only whe