add-pick-crew-rule

name	add-pick-crew-rule
description	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}.

Manage Crew Routing Rules

Crew routing rules live in defaults.crewRouting.rules inside ~/.config/squadrant/config.json. Each rule has the shape:

{
  "tier":  "<label>",      // human label, e.g. "extreme" / "hard" / "daily"
  "match": "<regex>",      // case-insensitive regex tested against the task text
  "agent": "claude|codex|gemini|opencode",
  "model": "opus|sonnet"   // omit for codex/opencode (they use their own defaults)
}

Rules are evaluated in order; the first match wins.

Adding a rule

1. Read the current config:

   cat ~/.config/squadrant/config.json
   

2. Identify the defaults.crewRouting.rules array. If it is absent, add it.

3. Build the new rule object. Validate:

   • tier is a non-empty string
   • match is a valid regex (test it mentally against a sample task string)
   • agent is one of claude, codex, gemini, opencode
   • model is only set for claude rules (opus or sonnet); omit for other agents

4. Insert the rule at the correct position — rules are evaluated in order. Higher-priority / more specific tiers (e.g. "extreme") belong before broader ones (e.g. "hard"). Append low-priority catch-alls last.

5. Write the updated config back via the existing save path:

   // The saveConfig helper in src/config.ts handles atomic write + newline.
   // If editing the live file directly, use JSON.stringify(config, null, 2) + "\n".
   

6. Verify the rule fires as expected:

   # Quick smoke-test (no live crew spawned):
   node -e "
     const {loadConfig} = require(process.env.HOME + '/.config/squadrant/node_modules/...');
     // or just log the matching rule manually
     const rules = require(process.env.HOME + '/.config/squadrant/config.json')
       .defaults?.crewRouting?.rules ?? [];
     const task = 'YOUR TEST TASK HERE';
     const hit = rules.find(r => new RegExp(r.match,'i').test(task));
     console.log(hit ?? 'no match');
   "
   

Editing an existing rule

Read → locate the rule by tier or match → update the field(s) → write back.

Removing a rule

Read → filter out the rule by tier or match → write back.

Precedence reminder

• Explicit --agent / --model on squadrant crew spawn always override routing.
• If no rule matches, the spawn falls through to defaults.roles.crew behavior (unchanged from pre-routing behavior).

Example rules

// Route deep-reasoning work to the strongest model
{ "tier": "extreme", "match": "redesign|architect|rewrite|from scratch|deep reasoning", "agent": "claude", "model": "opus" }

// Route standard feature/refactor work to a faster model
{ "tier": "hard",    "match": "refactor|migrate|implement|feature|daemon|control-plane", "agent": "claude", "model": "sonnet" }

// Route mobile tasks to codex (no model — uses codex default)
{ "tier": "mobile",  "match": "mobile|ios|swift|android|kotlin|react native", "agent": "codex" }

// Route trivial edits to opencode (cheapest path)
{ "tier": "daily",   "match": "typo|rename|bump|docs|comment|lint|format", "agent": "opencode" }