grok-routinglisted

When to delegate coding work to Grok Build vs handle it in Claude. Use whenever the user asks for bulk edits, test backfill, migrations, boilerplate, exploratory prototypes, or whether to use /grok:delegate — and when reviewing whether a task is safe to hand to Grok.
xzawed/claude-grok-build-plugin · ★ 1 · AI & Automation · score 74

Install: claude install-skill xzawed/claude-grok-build-plugin

# Grok routing (Claude orchestrates, Grok executes) You are in a session where the **grok** plugin can run Grok Build via MCP. Product goal: help the user **use Grok well**, **feel Grok’s strength**, and enjoy **Claude ↔ Grok collaboration** — not replace Claude. ## Default posture When a task is a good fit for Grok, **propose delegation first** (brief why + tool), then run it if the user agrees or already asked to use Grok. Do not dump every coding task on Grok. ## Delegate to Grok when | Fit | Examples | |---|---| | Bulk / repetitive | Same pattern across many files, renames, import fixes | | Low-risk volume | Test backfill, docs sync, boilerplate CRUD/DTO/scaffold | | Narrow independent scope | Single module, clear acceptance criteria, little monorepo coupling | | Exploratory prototype | Try an approach fast; user will review | **Tools (prefer this order):** 1. **Route first (no side effects):** `grok_build_route` or `/grok:route` — read **`nextAction`** (`handle_with_claude` | `call_mcp_tool` + tool/flags). Do not re-derive the plan. 2. If `nextAction.requiresHumanGateBeforeDelegate`: **plan** (`grok_build_plan` / `/grok:plan`) then wait for approval before any edit tool. 3. Execute: `grok_build_delegate` / `/grok:delegate` or verify `/grok:verify` as `nextAction.tool` says. 4. **Review gate:** `/grok:review` — diff + `billing`; never auto-commit. 5. Multi-turn: `/grok:resume` using `usage.lastSession.sessionId` or the last result’s `sessionId`. 6. Presets: `