Grok Build Orchestration

When to Use

• Use when delegating a well-specified implementation task to xAI's Grok Build CLI running headlessly
• Use when executing a Markdown implementation plan task-by-task with a diff review after each task
• Use when the user says "use grok", "grok build", "have grok implement", or "send to grok"

The coding assistant is the orchestrator: it plans, writes self-contained task specs, dispatches them to Grok Build headlessly, reviews every diff, and owns the final result. Grok is the fast, cheap executor. Full CLI details and verified behaviors: references/cli.md.

Safety Gate

Before every dispatch, show the user the exact task specification that will be sent to xAI, the target worktree, and the permission mode. Obtain explicit approval to disclose that text and to let Grok edit the scoped worktree. Never include secrets, proprietary source, customer data, or credentials in a task specification. Do not run grok update, --always-approve, or a destructive recovery command without separate, explicit approval.