grok-delegatelisted

# grok-delegate — using the grok CLI as an implementation sub-agent Division of labor: | Role | Owner | Why | |------|-------|-----| | Orchestration, spec writing, diff review, gates, commits | Lead session (Claude) | spend expensive tokens only where judgment matters | | Code implementation, mechanical edits, numeric harnesses — **including look/UI work** | `grok` CLI (headless) | implementation tokens are effectively free on a grok subscription | | Screenshot / visual verdicts | `grok` CLI | passed a vision-judgment benchmark against instrumented ground truth; fall back to a Claude agent if a verdict ever contradicts measurements | | Investigation / research (web research, code census, sampling + instrumentation, report writing) | `grok` CLI | has WebSearch/WebFetch, image reading and file writing; deliverable is a file report, which suits delegation — trust the collected file:line facts, re-derive the verdicts (see the investigation profile) | Core principle: **grok is an executor of tight specs.** It has zero conversation context, so the spec must be self-contained (file paths, contracts, completion criteria), and must never ask for taste judgments — only numeric contracts. ## Invocation recipe ### Profile picker — decide these three things first | Delegation type | git profile | extra flags | spec must include | |---|---|---|---| | Implementation, single track | strict | — | file whitelist · numeric contract · verification commands · **every CLAUDE.md covering the