菜单
Command playbook — invoked on-demand by `squadrant command [--task ...]`. Covers daily briefing, delegation workflow, project registration, status checking, and learnings review. Command is no longer always-on.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | command-ops |
| description | Command playbook — invoked on-demand by `squadrant command [--task ...]`. Covers daily briefing, delegation workflow, project registration, status checking, and learnings review. Command is no longer always-on. |
On-demand only. Command is no longer launched by
squadrant launch --all. You were spawned bysquadrant command --task <briefing|learnings-review|wiki-aggregate>to run a single task and exit. Do the task, then exit cleanly — no persistent loop.
Run when session starts, or user says "morning", "catch up", "summary":
for vault in $(cat ~/.config/squadrant/config.json | python3 -c "import json,sys; [print(p['spokeVault']) for p in json.loads(sys.stdin.read())['projects'].values()]"); do
echo "=== $(basename $vault) ==="
~/.config/squadrant/scripts/read-handoff.sh "$vault" --keep
done
Handoffs contain: currentState, openBranches, nextSteps, blockedItems, decisions. Use these to understand where each project left off.
mem-search skill) for recent activity across all projects.YESTERDAY=$(date -v-1d +"%Y-%m-%d")
for vault in $(cat ~/.config/squadrant/config.json | python3 -c "import json,sys; [print(p['spokeVault']) for p in json.loads(sys.stdin.read())['projects'].values()]"); do
echo "=== $vault ==="
cat "$vault/daily-logs/${YESTERDAY}.md" 2>/dev/null || echo "(no log)"
done
~/.config/squadrant/scripts/read-status.shsquadrant standup --yesterday --raw{hubVault}/daily-logs/YYYY-MM-DD.mdWhen the user gives a task for a project:
Match to ~/.config/squadrant/config.json.
/Applications/cmux.app/Contents/Resources/bin/cmux list-workspaces
CRITICAL: Match the EXACT captainName from config. Brove ≠ ⚓ brove-captain.
A name match is not sufficient — the workspace may be holding a session from a previous day. Check sessions.json against today before reusing:
TODAY=$(date +%Y-%m-%d)
LAST=$(python3 -c "import json; d=json.load(open('$HOME/.config/squadrant/sessions.json')); print(d.get('workspaces',{}).get('{captainName}',{}).get('lastLaunched',''))" 2>/dev/null)
[ "$LAST" = "$TODAY" ] && echo "fresh" || echo "stale"
fresh → reuse the existing workspace, proceed to step 5.stale (or no entry) → close the existing workspace, then go to step 4 to respawn so spawn-workspace.sh runs its ↻ new day — starting fresh session path:
/Applications/cmux.app/Contents/Resources/bin/cmux close-workspace --workspace "workspace:N"
Never skip this gate when a workspace was found by name — that's how stale captains get reused.
~/.config/squadrant/scripts/spawn-workspace.sh "{captainName}" "{projectPath}"
Wait a few seconds, then list-workspaces again to get its ref. Confirm the spawn logged ↻ new day — starting fresh session (or a clean first-launch) before sending work.
/Applications/cmux.app/Contents/Resources/bin/cmux send --workspace "workspace:N" "Task description with all context"
/Applications/cmux.app/Contents/Resources/bin/cmux send-key --workspace "workspace:N" Enter
"Delegated to {captainName}."
~/.config/squadrant/scripts/read-status.sh
Or read a captain's screen:
/Applications/cmux.app/Contents/Resources/bin/cmux read-screen --workspace "workspace:N"
find {path} -maxdepth 2 -name ".git" -type dsquadrant projects add {name} {path/to/repo} --group {group}
squadrant projects add {name}-docs {path/to/docs} --group {group} --group-role "documentation site"
.git directory, not the parent.Captains will send you reports via cmux send when tasks complete or blockers arise. When you receive a captain report:
You can also proactively check captain progress:
# Read all captain statuses at once
for vault in $(cat ~/.config/squadrant/config.json | python3 -c "import json,sys; [print(p['spokeVault']) for p in json.loads(sys.stdin.read())['projects'].values()]"); do
echo "=== $(basename $vault) ==="
head -15 "$vault/status.md" 2>/dev/null || echo "(no status)"
done
Do this when:
{spokeVault}/learnings/*.md where applied: falseapplied: truePeriodically review spoke wikis across all projects to build a cross-project knowledge base.
for vault in $(cat ~/.config/squadrant/config.json | python3 -c "import json,sys; [print(p['spokeVault']) for p in json.loads(sys.stdin.read())['projects'].values()]"); do
echo "=== $(basename $vault) ==="
cat "$vault/wiki/index.md" 2>/dev/null || echo "(no wiki)"
done
If a pattern appears in 2+ spoke wikis, create a hub-level wiki page that synthesizes both.
~/.config/squadrant/scripts/wiki-ingest.sh "{hubVaultPath}" "{slug}" "{title}" "{category}" "{body}" "{tags}" "aggregated from spoke wikis"
During daily briefing, check for:
Complete captain playbook — session startup, crew spawning, status writing, group awareness, and learnings. Use this skill at session start and reference it throughout.
Set up and manage the squadrant↔Telegram integration — bot setup, remote control, command-menu registration, and per-project notification tuning (mute, crew tiers, cap). Use when the user asks about Telegram setup, "why don't commands work", registering the /command menu, or muting/tuning notifications.
Add, edit, or remove a leveled crew routing rule in config.json without hand-editing JSON. Routing rules map task-text keywords to a tier → {agent, model}.
Reconcile squadrant config drift that needs human judgment — changed defaults and invalid values surfaced by `squadrant config check`. Use when the drift banner says "items need review" or the user asks to fix config drift.
Four coding principles derived from Andrej Karpathy's observations on LLM pitfalls. Use to reduce wrong assumptions, overengineering, drive-by refactors, and vague execution. Apply to every crew coding task and every captain review.
Read or set the global crew tokenomics dial (max | balance | low). Use when the user wants to change how aggressively crews consume tokens, or to check the current setting.