[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69BBDQ70BY1XPRF3RYV8FM6":3,"skill-same:01M69BBDQ70BY1XPRF3RYV8FM6":57},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":25,"linkOnly":26,"markdownContent":27,"markdownBody":28,"frontMatter":29,"refName":34,"commitSha":35,"skillDirectory":36,"forksCount":37,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":40,"ownerDescription":41,"updatedAt":42,"install":43,"resources":56},"01M69BBDQ70BY1XPRF3RYV8FM6","coordinator-init-mode",null,"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\u002F 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\u002Fteam.md exists.","microsoft\u002Ffsi-banking-payments-dispute-resolution-accelerator","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69BAVFSPPF5KP50DCBC2R4Q",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffsi-banking-payments-dispute-resolution-accelerator\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcoordinator-init-mode\u002FSKILL.md",[],[19,20,21,22,23,24],"init","coordinator init mode","init mode","merge","squad","create","2026-11-10 10:12:30",false,"---\nname: \"coordinator-init-mode\"\ndescription: \"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\u002F 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\u002Fteam.md exists.\"\nallowedTools: []\nconfidence: high\ndomain: squad-internals\nsource: \"Extracted from squad.agent.md as part of the slimming effort (bradygaster\u002Fsquad#1308). Behaviour unchanged — coordinator loads this satellite skill when init mode is detected (no .squad\u002Fteam.md present).\"\n---\n\n> **Load this skill when:** you detect that no `.squad\u002Fteam.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.\n>\n> **⚠️ Eager-execution exception:** Init Mode is the ONE exception to the eager-execution \u002F parallel-fan-out doctrine. Phase 1 MUST end with a user confirmation before any file is created. Do not bypass.\n\n## Phase 1: Propose the Team\n\nNo team exists yet. **Propose one — but DO NOT create any files until the user confirms.**\n\n1. **Identify the user.** Run `git config user.name` to learn who you're working with. Use their name in conversation (e.g., *\"Hey {user}, what are you building?\"*). Store their name (NOT email) in `team.md` under Project Context. **Never read or store `git config user.email`** — email addresses are PII and must not be written to committed files.\n2. Ask: *\"What are you building? (language, stack, what it does)\"*\n3. **Cast the team.** Before proposing names, run the Casting & Persistent Naming algorithm (see the canonical Casting reference at `.squad\u002Ftemplates\u002Fcasting-reference.md`):\n   - 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.\n   - Determine assignment shape from the user's project description.\n   - Derive resonance signals from the session and repo context.\n   - Select a universe. Allocate character names from that universe.\n   - Scribe is always \"Scribe\" — exempt from casting.\n   - Ralph is always \"Ralph\" — exempt from casting.\n   - Rai is always \"Rai\" — exempt from casting.\n   - Fact Checker is always \"Fact Checker\" — exempt from casting (same pattern as Scribe \u002F Ralph \u002F Rai).\n4. Propose the team with their cast names. Example (names will vary per cast):\n\n```\n?️  {CastName1}  — Lead          Scope, decisions, code review\n⚛️  {CastName2}  — Frontend Dev  React, UI, components\n?  {CastName3}  — Backend Dev   APIs, database, services\n?  {CastName4}  — Tester        Tests, quality, edge cases\n?  Scribe       — (silent)      Memory, decisions, session logs\n?  Ralph        — (monitor)     Work queue, backlog, keep-alive\n?️  Rai         — (background)  RAI awareness, content safety\n?  Fact Checker — (verifier)    Verification + Devil's Advocate\n```\n\n5. Use the `ask_user` tool to confirm the roster. Provide choices so the user sees a selectable menu:\n   - **question:** *\"Look right?\"*\n   - **choices:** `[\"Yes, hire this team\", \"Add someone\", \"Change a role\"]`\n\n**⚠️ STOP. Your response ENDS here. Do NOT proceed to Phase 2. Do NOT create any files or directories. Wait for the user's reply.**\n\n---\n\n## Phase 2: Create the Team\n\n**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\").\n\n> 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.**\n\n6. Create the `.squad\u002F` directory structure (see `.squad\u002Ftemplates\u002F` for format guides or use the standard structure: `team.md`, `routing.md`, `ceremonies.md`, `decisions.md`, `decisions\u002Finbox\u002F`, `casting\u002F`, `agents\u002F`, `orchestration-log\u002F`, `skills\u002F`, `log\u002F`, `rai\u002F`).\n\n**Casting state initialization:** Copy `.squad\u002Ftemplates\u002Fcasting-policy.json` to `.squad\u002Fcasting\u002Fpolicy.json` (or create from defaults). Create `registry.json` (entries: persistent_name, universe, created_at, legacy_named: false, status: \"active\") and `history.json` (first assignment snapshot with unique assignment_id).\n\n**Seeding:** Each agent's `history.md` starts with the project description, tech stack, and the user's name so they have day-1 context. Agent folder names are the cast name in lowercase (e.g., `.squad\u002Fagents\u002Fripley\u002F`). The Scribe's charter includes maintaining `decisions.md` and cross-agent context sharing. Rai's charter is seeded from the `Rai-charter.md` template, and `.squad\u002Frai\u002Fpolicy.md` is seeded from `rai-policy.md`. Fact Checker's charter is seeded from `fact-checker-charter.md` and `.squad\u002Ffact-checker\u002Fpolicy.md` is seeded from `fact-checker-policy.md`.\n\n**Team.md structure:** `team.md` MUST contain a section titled exactly `## Members` (not \"## Team Roster\" or other variations) containing the roster table. This header is hard-coded in GitHub workflows (`squad-heartbeat.yml`, `squad-issue-assign.yml`, `squad-triage.yml`, `sync-squad-labels.yml`) for label automation. If the header is missing or titled differently, label routing breaks.\n\n**Merge driver for append-only files:** Create or update `.gitattributes` at the repo root to enable conflict-free merging of `.squad\u002F` state across branches:\n\n```\n.squad\u002Fdecisions.md merge=union\n.squad\u002Fagents\u002F*\u002Fhistory.md merge=union\n.squad\u002Flog\u002F** merge=union\n.squad\u002Forchestration-log\u002F** merge=union\n.squad\u002Frai\u002Faudit-trail.md merge=union\n```\n\nThe `union` merge driver keeps all lines from both sides, which is correct for append-only files. This makes worktree-local strategy work seamlessly when branches merge — decisions, memories, and logs from all branches combine automatically.\n\n7. Say: *\"✅ Team hired. Try: '{FirstCastName}, set up the project structure'\"*\n\n8. **Post-setup input sources** (optional — ask after team is created, not during casting):\n   - **PRD\u002Fspec:** *\"Do you have a PRD or spec document? (file path, paste it, or skip)\"* → If provided, follow PRD Mode flow.\n   - **GitHub issues:** *\"Is there a GitHub repo with issues I should pull from? (owner\u002Frepo, or skip)\"* → If provided, follow GitHub Issues Mode flow.\n   - **Human members:** *\"Are any humans joining the team? (names and roles, or just AI for now)\"* → If provided, add per Human Team Members section.\n   - **Copilot agent:** *\"Want to include @copilot? It can pick up issues autonomously. (yes\u002Fno)\"* → If yes, follow Copilot Coding Agent Member section and ask about auto-assignment.\n   - These are additive. **Don't block** — if the user skips or gives a task instead, proceed immediately.\n","> **Load this skill when:** you detect that no `.squad\u002Fteam.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.\n>\n> **⚠️ Eager-execution exception:** Init Mode is the ONE exception to the eager-execution \u002F parallel-fan-out doctrine. Phase 1 MUST end with a user confirmation before any file is created. Do not bypass.\n\n## Phase 1: Propose the Team\n\nNo team exists yet. **Propose one — but DO NOT create any files until the user confirms.**\n\n1. **Identify the user.** Run `git config user.name` to learn who you're working with. Use their name in conversation (e.g., *\"Hey {user}, what are you building?\"*). Store their name (NOT email) in `team.md` under Project Context. **Never read or store `git config user.email`** — email addresses are PII and must not be written to committed files.\n2. Ask: *\"What are you building? (language, stack, what it does)\"*\n3. **Cast the team.** Before proposing names, run the Casting & Persistent Naming algorithm (see the canonical Casting reference at `.squad\u002Ftemplates\u002Fcasting-reference.md`):\n   - 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.\n   - Determine assignment shape from the user's project description.\n   - Derive resonance signals from the session and repo context.\n   - Select a universe. Allocate character names from that universe.\n   - Scribe is always \"Scribe\" — exempt from casting.\n   - Ralph is always \"Ralph\" — exempt from casting.\n   - Rai is always \"Rai\" — exempt from casting.\n   - Fact Checker is always \"Fact Checker\" — exempt from casting (same pattern as Scribe \u002F Ralph \u002F Rai).\n4. Propose the team with their cast names. Example (names will vary per cast):\n\n```\n?️  {CastName1}  — Lead          Scope, decisions, code review\n⚛️  {CastName2}  — Frontend Dev  React, UI, components\n?  {CastName3}  — Backend Dev   APIs, database, services\n?  {CastName4}  — Tester        Tests, quality, edge cases\n?  Scribe       — (silent)      Memory, decisions, session logs\n?  Ralph        — (monitor)     Work queue, backlog, keep-alive\n?️  Rai         — (background)  RAI awareness, content safety\n?  Fact Checker — (verifier)    Verification + Devil's Advocate\n```\n\n5. Use the `ask_user` tool to confirm the roster. Provide choices so the user sees a selectable menu:\n   - **question:** *\"Look right?\"*\n   - **choices:** `[\"Yes, hire this team\", \"Add someone\", \"Change a role\"]`\n\n**⚠️ STOP. Your response ENDS here. Do NOT proceed to Phase 2. Do NOT create any files or directories. Wait for the user's reply.**\n\n---\n\n## Phase 2: Create the Team\n\n**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\").\n\n> 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.**\n\n6. Create the `.squad\u002F` directory structure (see `.squad\u002Ftemplates\u002F` for format guides or use the standard structure: `team.md`, `routing.md`, `ceremonies.md`, `decisions.md`, `decisions\u002Finbox\u002F`, `casting\u002F`, `agents\u002F`, `orchestration-log\u002F`, `skills\u002F`, `log\u002F`, `rai\u002F`).\n\n**Casting state initialization:** Copy `.squad\u002Ftemplates\u002Fcasting-policy.json` to `.squad\u002Fcasting\u002Fpolicy.json` (or create from defaults). Create `registry.json` (entries: persistent_name, universe, created_at, legacy_named: false, status: \"active\") and `history.json` (first assignment snapshot with unique assignment_id).\n\n**Seeding:** Each agent's `history.md` starts with the project description, tech stack, and the user's name so they have day-1 context. Agent folder names are the cast name in lowercase (e.g., `.squad\u002Fagents\u002Fripley\u002F`). The Scribe's charter includes maintaining `decisions.md` and cross-agent context sharing. Rai's charter is seeded from the `Rai-charter.md` template, and `.squad\u002Frai\u002Fpolicy.md` is seeded from `rai-policy.md`. Fact Checker's charter is seeded from `fact-checker-charter.md` and `.squad\u002Ffact-checker\u002Fpolicy.md` is seeded from `fact-checker-policy.md`.\n\n**Team.md structure:** `team.md` MUST contain a section titled exactly `## Members` (not \"## Team Roster\" or other variations) containing the roster table. This header is hard-coded in GitHub workflows (`squad-heartbeat.yml`, `squad-issue-assign.yml`, `squad-triage.yml`, `sync-squad-labels.yml`) for label automation. If the header is missing or titled differently, label routing breaks.\n\n**Merge driver for append-only files:** Create or update `.gitattributes` at the repo root to enable conflict-free merging of `.squad\u002F` state across branches:\n\n```\n.squad\u002Fdecisions.md merge=union\n.squad\u002Fagents\u002F*\u002Fhistory.md merge=union\n.squad\u002Flog\u002F** merge=union\n.squad\u002Forchestration-log\u002F** merge=union\n.squad\u002Frai\u002Faudit-trail.md merge=union\n```\n\nThe `union` merge driver keeps all lines from both sides, which is correct for append-only files. This makes worktree-local strategy work seamlessly when branches merge — decisions, memories, and logs from all branches combine automatically.\n\n7. Say: *\"✅ Team hired. Try: '{FirstCastName}, set up the project structure'\"*\n\n8. **Post-setup input sources** (optional — ask after team is created, not during casting):\n   - **PRD\u002Fspec:** *\"Do you have a PRD or spec document? (file path, paste it, or skip)\"* → If provided, follow PRD Mode flow.\n   - **GitHub issues:** *\"Is there a GitHub repo with issues I should pull from? (owner\u002Frepo, or skip)\"* → If provided, follow GitHub Issues Mode flow.\n   - **Human members:** *\"Are any humans joining the team? (names and roles, or just AI for now)\"* → If provided, add per Human Team Members section.\n   - **Copilot agent:** *\"Want to include @copilot? It can pick up issues autonomously. (yes\u002Fno)\"* → If yes, follow Copilot Coding Agent Member section and ask about auto-assignment.\n   - These are additive. **Don't block** — if the user skips or gives a task instead, proceed immediately.\n",{"name":5,"domain":30,"source":31,"confidence":32,"description":7,"allowedTools":33},"squad-internals","Extracted from squad.agent.md as part of the slimming effort (bradygaster\u002Fsquad#1308). Behaviour unchanged — coordinator loads this satellite skill when init mode is detected (no .squad\u002Fteam.md present).","high",[],"main","5494201db9619bc6c0de7999caa5ae7ae315e6be",".github\u002Fskills\u002Fcoordinator-init-mode",3,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffsi-banking-payments-dispute-resolution-accelerator","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-10-27 01:08:00",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add microsoft\u002Ffsi-banking-payments-dispute-resolution-accelerator --skill coordinator-init-mode",{"tool":49,"command":50},"bunx","bunx skills add microsoft\u002Ffsi-banking-payments-dispute-resolution-accelerator --skill coordinator-init-mode",{"tool":52,"command":53},"pnpm","pnpm dlx skills add microsoft\u002Ffsi-banking-payments-dispute-resolution-accelerator --skill coordinator-init-mode","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffsi-banking-payments-dispute-resolution-accelerator\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcoordinator-init-mode\u002FSKILL.md",true,[],[58,73,80,86,100,114],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":69,"publishedAt":25},"01M69BCQ2R27TFYA8Q03XFNFWM","{skill-name}","{what this skill teaches agents}","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffsi-banking-payments-dispute-resolution-accelerator\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskill.md",[64],{"categoryNo":65,"categoryName":66,"taxonomyType":67,"taxonomyTypeDesc":68},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[70,71,72],"{skill name}","testing","design",{"skillNo":74,"name":75,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":25},"01M69BCNFGJTKKASKWDB0MM668","azd-seed-hook","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffsi-banking-payments-dispute-resolution-accelerator\u002Fblob\u002Fmain\u002F.squad\u002Fskills\u002Fazd-seed-hook\u002FSKILL.md",[],[79],"azd seed hook",{"skillNo":81,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":85,"publishedAt":25},"01M69BCDES6M5FRTCMY7214B94","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffsi-banking-payments-dispute-resolution-accelerator\u002Fblob\u002Fmain\u002F.squad\u002Fskill.md",[84],{"categoryNo":65,"categoryName":66,"taxonomyType":67,"taxonomyTypeDesc":68},[70,71,72],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":96,"publishedAt":25},"01M69BCBAGT24AD5SBDP876P09","tiered-memory","Three-tier agent memory model (hot\u002Fcold\u002Fwiki) for context reduction per spawn","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffsi-banking-payments-dispute-resolution-accelerator\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftiered-memory\u002FSKILL.md",[92,95],{"categoryNo":93,"categoryName":94,"taxonomyType":67,"taxonomyTypeDesc":68},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":65,"categoryName":66,"taxonomyType":67,"taxonomyTypeDesc":68},[97,98,72,99],"memory","tiered memory","performance",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":109,"publishedAt":25},"01M69BC9SWSK7ZX02AKTVT16E9","test-discipline","Update tests when changing APIs — no exceptions","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffsi-banking-payments-dispute-resolution-accelerator\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftest-discipline\u002FSKILL.md",[106],{"categoryNo":107,"categoryName":108,"taxonomyType":67,"taxonomyTypeDesc":68},"01JBSEEDCAT000000000000008","测试与质量",[110,111,112,113],"test discipline","test","sync","update",{"skillNo":115,"name":23,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":25},"01M69BC7MR12QTSH97DCQYB81N","Squad's command catalog and interactive menu. Invoke via \u002Fsquad (slash command) or natural language (\"squad commands\", \"what can squad do\", \"show me squad options\"). Presents categorized operations (Install & Upgrade, Team Management, Issues & PRs, Plugins & Skills, Model & Cost, Sessions & State) as an interactive picker. Routes to the right squad CLI command or the Squad coordinator agent.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffsi-banking-payments-dispute-resolution-accelerator\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fsquad\u002FSKILL.md",[],[23,120,121,122],"cli","squad commands","sessions"]