shaq

Provider routing — DO THIS FIRST

Shaq may be pinned to a non-Claude provider (see model.provider / /admin/models). Resolve it:

DT="$(cat ~/.claude/dreamteam/repo-root 2>/dev/null)"; [ -d "$DT" ] || DT="$(git rev-parse --show-toplevel 2>/dev/null)"
PROV="$([ -d "$DT" ] && bun "$DT/scripts/print-provider.ts" shaq 2>/dev/null || echo claude)"; echo "shaq → $PROV"

• $PROV = claude (or unresolved) → spawn the shaq subagent via the Task tool (subagent_type="shaq") with the mission below. Native, on Max. (unchanged behavior)

• $PROV = codex | ollama → implementation is delegated; you MUST run the two-phase plan → approve → implement gate (the plan phase is write-incapable per provider, so it physically cannot write before you approve):

  1. Plan (write-incapable):

     BRIEF="$(mktemp)"; cat > "$BRIEF" <<'BRIEF_EOF'
     [The implementation task: $ARGUMENTS + the Output Requirements below.]
     BRIEF_EOF
     bun "$DT/evals/src/team-dispatch.ts" shaq "$BRIEF" --phase plan > /tmp/shaq-plan.json
     

     Present the plan (.output) to the user.
  2. Approve (MANDATORY checkpoint): use AskUserQuestion — approve / revise / abort. Do NOT proceed without go-ahead (the same gate native Shaq's plan mode enforces).
  3. Implement (writes to a sandbox, not the repo):

     bun -e 'require("fs").writeFileSync("/tmp/shaq-plan.txt", require("/tmp/shaq-plan.json").output||"")'
     bun "$DT/evals/src/team-dispatch.ts" shaq "$BRIEF" --phase implement --plan /tmp/shaq-plan.txt
     

     .writtenFiles are in .artifactsDir (the session sandbox). Review the diff and promote into the repo ONLY on your approval (BR-10). On ok:false, report .error (fail-loud — never silently fall back to Claude).

---

CRITICAL (native/claude path only): spawn an agent using the Task tool with subagent_type="shaq" to enable color-coded parallel execution. NEVER respond directly on the claude path — always use the Task tool.

---

You are invoking Shaq (Shaquille O'Neal) — the Primary Code Executor.