[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADADA9HC3085KSQJ7RBHWR":3,"skill-same:01M6ADADA9HC3085KSQJ7RBHWR":76},{"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":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":51,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M6ADADA9HC3085KSQJ7RBHWR","init-mode",null,"Team initialization flow (Phase 1 proposal + Phase 2 creation)","github\u002Fgh-aw","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3VCZ4WKQSFSRTPN7N9DN",5621,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Finit-mode\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"init","init mode","mode","orchestration","flow","team","ask","confirmation","user","creation","proposal","roster","with","high","initialization","phase","2026-11-10 10:12:30",false,"---\nname: \"init-mode\"\ndescription: \"Team initialization flow (Phase 1 proposal + Phase 2 creation)\"\ndomain: \"orchestration\"\nconfidence: \"high\"\nsource: \"extracted\"\ntools:\n  - name: \"ask_user\"\n    description: \"Confirm team roster with selectable menu\"\n    when: \"Phase 1 proposal — requires explicit user confirmation\"\n---\n\n## Context\n\nInit Mode activates when `.squad\u002Fteam.md` does not exist, or exists but has zero roster entries under `## Members`. The coordinator proposes a team (Phase 1), waits for user confirmation, then creates the team structure (Phase 2).\n\n## Patterns\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 that section):\n   - Determine team size (typically 4–5 + Scribe).\n   - **Default to descriptive names** (Lead, Frontend, Backend, Tester, etc.) unless the user requests a themed universe.\n   - If the user requests a specific universe (built-in or custom), allocate character names from that universe. For custom universes not in the allowlist, use your knowledge of the source material and apply spoiler-safety rules.\n   - If the user asks for themed names without specifying a universe, auto-select from built-in universes using the scoring algorithm (size_fit + shape_fit + resonance_fit + LRU).\n   - Scribe is always \"Scribe\" — exempt from casting.\n   - Ralph is always \"Ralph\" — exempt from casting.\n4. Propose the team with their cast names. Example (names will vary per cast):\n\n```\n?️  Lead         — Lead          Scope, decisions, code review\n⚛️  Frontend     — Frontend Dev  React, UI, components\n?  Backend      — Backend Dev   APIs, database, services\n?  Tester       — Tester        Tests, quality, edge cases\n?  Scribe       — (silent)      Memory, decisions, session logs\n?  Ralph        — (monitor)     Work queue, backlog, keep-alive\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, cast 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### 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).\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.\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.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```\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 cast. 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\n## Examples\n\n**Example flow:**\n1. Coordinator detects no team.md → Init Mode\n2. Runs `git config user.name` → \"{user}\"\n3. Asks: *\"Hey {user}, what are you building?\"*\n4. User: *\"TypeScript CLI tool with GitHub API integration\"*\n5. Coordinator uses descriptive naming by default\n6. Proposes: Lead (Lead), Frontend (Frontend Dev), Backend (Backend Dev), Tester (Tester), Scribe, Ralph\n7. Uses `ask_user` with choices → user selects \"Yes, cast this team\"\n8. Coordinator creates `.squad\u002F` structure, initializes casting state, seeds agents\n9. Says: *\"✅ Team cast. Try: 'Lead, set up the project structure'\"*\n\n## Anti-Patterns\n\n- ❌ Creating files before user confirms Phase 1\n- ❌ Mixing agents from different universes in the same cast\n- ❌ Skipping the `ask_user` tool and assuming confirmation\n- ❌ Proceeding to Phase 2 when user said \"add someone\" or \"change a role\"\n- ❌ Using `## Team Roster` instead of `## Members` as the header (breaks GitHub workflows)\n- ❌ Forgetting to initialize `.squad\u002Fcasting\u002F` state files\n- ❌ Reading or storing `git config user.email` (PII violation)\n- ❌ Rejecting a user's universe choice because it is not in the built-in allowlist\n- ❌ Auto-selecting a themed universe when the user didn't ask for one (use descriptive names by default)\n","## Context\n\nInit Mode activates when `.squad\u002Fteam.md` does not exist, or exists but has zero roster entries under `## Members`. The coordinator proposes a team (Phase 1), waits for user confirmation, then creates the team structure (Phase 2).\n\n## Patterns\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 that section):\n   - Determine team size (typically 4–5 + Scribe).\n   - **Default to descriptive names** (Lead, Frontend, Backend, Tester, etc.) unless the user requests a themed universe.\n   - If the user requests a specific universe (built-in or custom), allocate character names from that universe. For custom universes not in the allowlist, use your knowledge of the source material and apply spoiler-safety rules.\n   - If the user asks for themed names without specifying a universe, auto-select from built-in universes using the scoring algorithm (size_fit + shape_fit + resonance_fit + LRU).\n   - Scribe is always \"Scribe\" — exempt from casting.\n   - Ralph is always \"Ralph\" — exempt from casting.\n4. Propose the team with their cast names. Example (names will vary per cast):\n\n```\n?️  Lead         — Lead          Scope, decisions, code review\n⚛️  Frontend     — Frontend Dev  React, UI, components\n?  Backend      — Backend Dev   APIs, database, services\n?  Tester       — Tester        Tests, quality, edge cases\n?  Scribe       — (silent)      Memory, decisions, session logs\n?  Ralph        — (monitor)     Work queue, backlog, keep-alive\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, cast 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### 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).\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.\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.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```\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 cast. 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\n## Examples\n\n**Example flow:**\n1. Coordinator detects no team.md → Init Mode\n2. Runs `git config user.name` → \"{user}\"\n3. Asks: *\"Hey {user}, what are you building?\"*\n4. User: *\"TypeScript CLI tool with GitHub API integration\"*\n5. Coordinator uses descriptive naming by default\n6. Proposes: Lead (Lead), Frontend (Frontend Dev), Backend (Backend Dev), Tester (Tester), Scribe, Ralph\n7. Uses `ask_user` with choices → user selects \"Yes, cast this team\"\n8. Coordinator creates `.squad\u002F` structure, initializes casting state, seeds agents\n9. Says: *\"✅ Team cast. Try: 'Lead, set up the project structure'\"*\n\n## Anti-Patterns\n\n- ❌ Creating files before user confirms Phase 1\n- ❌ Mixing agents from different universes in the same cast\n- ❌ Skipping the `ask_user` tool and assuming confirmation\n- ❌ Proceeding to Phase 2 when user said \"add someone\" or \"change a role\"\n- ❌ Using `## Team Roster` instead of `## Members` as the header (breaks GitHub workflows)\n- ❌ Forgetting to initialize `.squad\u002Fcasting\u002F` state files\n- ❌ Reading or storing `git config user.email` (PII violation)\n- ❌ Rejecting a user's universe choice because it is not in the built-in allowlist\n- ❌ Auto-selecting a themed universe when the user didn't ask for one (use descriptive names by default)\n",{"name":5,"tools":40,"domain":22,"source":45,"confidence":32,"description":7},[41],{"name":42,"when":43,"description":44},"ask_user","Phase 1 proposal — requires explicit user confirmation","Confirm team roster with selectable menu","extracted","main","8541229759617347888641eba917d3b0ad66a984",".squad\u002Ftemplates\u002Fskills\u002Finit-mode",625,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw","https:\u002F\u002Fgh.io\u002Fgh-aw","https:\u002F\u002Fgithub.com\u002Fgithub","https:\u002F\u002Fgithub.com\u002Fabout","How people build software.","2026-11-12 03:23:28",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add github\u002Fgh-aw --skill init-mode",{"tool":62,"command":63},"bunx","bunx skills add github\u002Fgh-aw --skill init-mode",{"tool":65,"command":66},"pnpm","pnpm dlx skills add github\u002Fgh-aw --skill init-mode","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Finit-mode\u002FSKILL.md",true,[70],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"agents\u002Fopenai.yaml","REFERENCE","参考文档",168,"https:\u002F\u002Fgithub.com\u002Fajrussellaudio\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002F.claude\u002Fskills\u002Fimplement-spec\u002Fagents\u002Fopenai.yaml",[77,106,123,148,173,191],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":91,"publishedAt":35},"01M6ADC942STTXHFV410J4DH0X","GitHub Agentic Workflows","GitHub Agentic Workflows (`gh-aw`) is a GitHub CLI extension for writing Agentic Workflows in markdown and compiling them to GitHub Actions.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002FSKILL.md",[83,88],{"categoryNo":84,"categoryName":85,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",{"categoryNo":89,"categoryName":90,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000023","Skill与智能体开发",[9,92,93,94,95,96,97,98,99,100,101,102,103,104,105],"agentic","agentic workflows","github agentic workflows","workflows","github cli","gh","extension","for","compiling","cli","writing","actions","github actions","markdown",{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":35},"01M6ADC6ZXSA46N9XD6VNAP1MS","windows-compatibility","Cross-platform path handling and command patterns","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Fwindows-compatibility\u002FSKILL.md",[],[113,114,115,116,117,32,118,119,120,121,122],"windows","windows compatibility","compatibility","bugs","path","platform","cross-platform","patterns","command","git",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":35},"01M6ADC44957SVQF96R5YY247P","versioning-policy","Semver versioning rules for Squad SDK and CLI — prevents prerelease version incidents","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Fversioning-policy\u002FSKILL.md",[],[130,131,132,133,134,135,136,137,138,139,140,141,142,143,144,145,99,146,101,147],"policy","versioning policy","versioning","incident","gate","implementation","version","Rules","workspace","pr","ci","npm","semver","release","squad","resolution","incidents","sdk",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":158,"publishedAt":35},"01M6ADC1PHMEAEVR87F8PDR89X","tiered-memory","Three-tier agent memory model (hot\u002Fcold\u002Fwiki) for context reduction per spawn","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Ftiered-memory\u002FSKILL.md",[154,157],{"categoryNo":155,"categoryName":156,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":89,"categoryName":90,"taxonomyType":86,"taxonomyTypeDesc":87},[159,160,161,162,99,163,29,164,165,166,167,168,169,170,171,172],"tiered memory","memory","memory-management","model","cold","runtime","three","spawn","management","context","wiki","agent memory","performance","design",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":182,"publishedAt":35},"01M6ADBZTDGFM0E25EWRQEMYEH","test-discipline","Update tests when changing APIs — no exceptions","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Ftest-discipline\u002FSKILL.md",[179],{"categoryNo":180,"categoryName":181,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000008","测试与质量",[183,184,185,186,187,32,188,133,189,190],"test discipline","discipline","test","sync","when","tests","quality","update",{"skillNo":192,"name":144,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":194,"categories":195,"keywords":196,"publishedAt":35},"01M6ADBX5MJP4Z7CG4XTV8ZVT8","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\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Fsquad\u002FSKILL.md",[],[144,197,198,199,200,201,202,203,204,205,206,207,208,121,162,24,209,210,211,212,213,214,101],"show","interactive menu","invoke","coordinator","as","commands","upgrade","options","me","natural language","do","install","show me","plugins","issues","state","squad commands","sessions"]