squad-commands

Menu Presentation Rules

When the user triggers this skill ("squad commands", "help", "what can squad do", etc.):

1. Category-level menu first. Present category names as an ask_user choice list:

   📋 Squad Commands — pick a category:
   1. Install & Upgrade
   2. Team Management
   3. Issues & PRs
   4. Plugins & Skills
   5. Model & Cost
   6. Sessions & State
   

2. Drill-down. After selection, show operation titles in that category as a second ask_user list.
3. Direct match skips the menu. If the user says "how do I upgrade with state backend," match to the specific entry and go straight to argument collection.
4. Compact fallback. If ask_user is unavailable, render as a markdown table instead.
5. Back / Cancel. Include "← Back to categories" in sub-menus. Include "Cancel" in confirmation prompts. Respect "never mind" / "cancel" at any point.

Argument collection: For entries with args, iterate the list sequentially. Use ask_user with choices when choices is provided; free-text prompt otherwise. If the user says "just do it" or "defaults are fine," skip remaining args and use their defaults.

Confirmation template:

⚠️ This will {action-description}.
{what will change}
Proceed? (yes / no)

---

Install & Upgrade

Upgrade Squad CLI

• intent: upgrade squad, update squad, install latest version, get new version
• summary: Upgrade Squad CLI to the latest version for your channel
• action: shell
• command: squad upgrade
• args:
  • state-backend: Which state backend? | choices: {worktree, git-notes, orphan, two-layer} | default: (keep current)
• confirm: false
• platform_caveats: Requires terminal. In VS Code, open the integrated terminal and run the command directly.

Initialize Squad

• intent: set up squad, initialize squad, create team, start squad in this project
• summary: Scaffold Squad in the current directory (idempotent)
• action: shell
• command: squad init
• args: (none)
• confirm: false
• platform_caveats: Requires terminal. Recommend a standalone terminal for best results.