AGENT SKILL

squad-coordinator-init-mode

Squad coordinator only: Init Mode, proposing and casting a new team. Load when team.md is missing or has an empty roster, or when asked to set up or cast a team.

License 许可
MIT
所属仓库
github/squad
最近更新
2026-11-15
Stars
★ 3.4k
Forks
520

01 前言 Front Matter

name
squad-coordinator-init-mode
description
Squad coordinator only: Init Mode, proposing and casting a new team. Load when team.md is missing or has an empty roster, or when asked to set up or cast a team.

03 SKILL.md 正文

<!-- Generated by Squad from the Squad SDK (claude-plugin.ts). Do not edit: run node scripts/build-claude-plugin.mjs. -->

Init Mode and casting

This is the full text of core-protocol item 0 of the Squad coordinator, loaded on demand. It applies only to the Squad coordinator, never to team members.

Init Mode (only when there is truly no team). Decide this with squad_state_read of team.md (or squad_state_list), NEVER with glob/grep/search tools: many hosts' glob/grep skip dot-directories like .squad/ and will wrongly report "no matches". If team.md is readable and lists members, a team exists: NEVER overwrite or re-cast it, or its charters, decisions, history or casting records; use it. Only if team.md does not exist or has an empty roster:

  • Phase 1 (propose). Infer the project's purpose from the request and repository (ask only if it is genuinely unknowable AND the session is interactive). Propose 3-5 specialists with a thematic universe, names and roles (a Lead, domain implementers, a Tester; Scribe, Ralph, Rai and Fact Checker are always-on built-ins).
  • Auto-confirm (default). Do NOT stop to ask questions in Init Mode. The user's request is the confirmation: pick sensible defaults for anything unspecified (stack, scope, universe), record those assumptions under Project Context in team.md, and continue to Phase 2 in the SAME turn. This is mandatory when the user said to proceed / confirm / go, or the host runs headless (print / exec / no question tool). Only an interactive session with a genuinely unknowable purpose may ask, and then at most ONE short question. Never end the turn with only a proposal or questions.
  • Phase 2 (create). If you can run shell commands, add EVERY member with the CLI, one call each: squad cast --name <Name> --role "<Role>" (or, when squad is not on PATH, node .squad/squad.mjs cast --name <Name> --role "<Role>"; not npx squad, which may fetch an old published version and needs an approval prompt) (it writes the charter, history, the team.md roster row, routing hooks and the casting registry/history pair correctly; the built-ins scribe, ralph, rai and fact-checker already exist after squad init). Then write/adjust .squad/routing.md as an ordinary file, and once routing is written run squad client sync so host files built from it (Claude Code member subagent descriptions) pick up who owns what; it rewrites only Squad-managed files. If a cast command is denied, stop: show the exact squad cast commands and ask the user to allow them (in Claude Code, by trusting the folder, which turns on the allow rules Squad wrote) or run them, then continue; never write the members yourself instead. If squad cast --name is not recognised (an older squad build that only lists the cast), tell the user to upgrade the squad CLI instead of hand-writing the team. NEVER hand-write or edit anything under .squad/casting/ (registry.json, history.json, registry-history.commit.json are a checksummed pair: manual edits make squad upgrade fail with a registry error). If you cannot run shell commands, write team.md (a markdown table with Name, Role, Charter, Status columns; the Coordinator row stays separate), .squad/agents/<lowercase-name>/charter.md and history.md as ordinary files, leave .squad/casting/ untouched and tell the user to run squad cast --name <Name> --role "<Role>" for each member to register them.
  • After casting, STOP and report the roster unless the user's request also asked for work (setting up the team is not a request to build anything).
  • Scratch space. Use .squad/scratch/ (inside the workspace) for temporary files; never write outside the workspace directory (hosts reject external-directory access).

04 同仓库更多 Skills