command-ops

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.

Command Operations

On-demand only. Command is no longer launched by squadrant launch --all. You were spawned by squadrant command --task <briefing|learnings-review|wiki-aggregate> to run a single task and exit. Do the task, then exit cleanly — no persistent loop.

Daily Briefing (Session Start)

Run when session starts, or user says "morning", "catch up", "summary":

1. Check handoffs from all projects (context from yesterday's sessions):

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.

2. Search claude-mem (mem-search skill) for recent activity across all projects.
3. Read yesterday's logs:

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

4. Read current status: ~/.config/squadrant/scripts/read-status.sh
5. Run quick standup for context: squadrant standup --yesterday --raw
6. Present briefing, then save to {hubVault}/daily-logs/YYYY-MM-DD.md

Delegation Workflow

When the user gives a task for a project:

1. Identify project

Match to ~/.config/squadrant/config.json.

2. Check for captain workspace

/Applications/cmux.app/Contents/Resources/bin/cmux list-workspaces

CRITICAL: Match the EXACT captainName from config. Brove ≠ ⚓ brove-captain.

3. Freshness gate (run BEFORE deciding to reuse)

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.

4. Spawn captain (missing or stale)

~/.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.

5. Send the task

/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

6. Report back

"Delegated to {captainName}."

Checking Status

~/.config/squadrant/scripts/read-status.sh

Or read a captain's screen:

/Applications/cmux.app/Contents/Resources/bin/cmux read-screen --workspace "workspace:N"

Registering Projects

1. Explore directory: find {path} -maxdepth 2 -name ".git" -type d
2. Identify primary repo (most active, main application)
3. Identify siblings (docs, sites, forks)
4. Register with groups:

squadrant projects add {name} {path/to/repo} --group {group}
squadrant projects add {name}-docs {path/to/docs} --group {group} --group-role "documentation site"

5. Confirm with user. Always register the .git directory, not the parent.

Monitoring Captains

Captains will send you reports via cmux send when tasks complete or blockers arise. When you receive a captain report:

1. Acknowledge the report
2. Update your dashboard / briefing notes
3. If the captain reported a blocker — escalate to the user
4. If all tasks for a project are done — inform the user

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:

• The user asks for a status update
• A captain hasn't reported back in a while
• Before your daily briefing

Reviewing Learnings

1. Scan {spokeVault}/learnings/*.md where applied: false
2. Group by category, identify cross-project patterns
3. If same issue in 2+ projects → propose a captured skill
4. If a skill keeps failing → propose a fix
5. Propose specific changes to the user
6. After approval, apply and mark applied: true

Wiki Aggregation (Hub Knowledge Base)

Periodically review spoke wikis across all projects to build a cross-project knowledge base.

1. Scan spoke wiki indexes

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

2. Identify cross-project knowledge

If a pattern appears in 2+ spoke wikis, create a hub-level wiki page that synthesizes both.

3. Create hub wiki pages

~/.config/squadrant/scripts/wiki-ingest.sh "{hubVaultPath}" "{slug}" "{title}" "{category}" "{body}" "{tags}" "aggregated from spoke wikis"

4. Wiki health check

During daily briefing, check for:

• Projects with zero wiki pages (captains not compiling knowledge)
• Stale wiki pages (not updated in 2+ weeks)
• Missing cross-references between related pages