Executing Plans Inline
obra/superpowers
Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.
Orchestrate coding work by delegating well-specified implementation tasks to xAI's Grok Build CLI (grok) running headlessly, while the coding assistant plans, writes the task specs, reviews every…
Install Grok Build
$ npx skills add sanjay3290/ai-skills --skill grok-build -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sanjay3290/ai-skills grok-build --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/sanjay3290/ai-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/grok-build .claude/skills/grok-build && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "grok-build" agent skill from https://github.com/sanjay3290/ai-skills/tree/main/skills/grok-build into .claude/skills/grok-build/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grok-build", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/sanjay3290/ai-skills/tree/main/skills/grok-buildType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add sanjay3290/ai-skills --skill grok-build -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sanjay3290/ai-skills grok-build --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sanjay3290/ai-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/grok-build .agents/skills/grok-build && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "grok-build" agent skill from https://github.com/sanjay3290/ai-skills/tree/main/skills/grok-build into .agents/skills/grok-build/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grok-build", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sanjay3290/ai-skills --skill grok-build -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sanjay3290/ai-skills grok-build --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sanjay3290/ai-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/grok-build .cursor/skills/grok-build && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "grok-build" agent skill from https://github.com/sanjay3290/ai-skills/tree/main/skills/grok-build into .cursor/skills/grok-build/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grok-build", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/sanjay3290/ai-skills.git --path skills/grok-build--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add sanjay3290/ai-skills --skill grok-build -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sanjay3290/ai-skills grok-build --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sanjay3290/ai-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/grok-build .gemini/skills/grok-build && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "grok-build" agent skill from https://github.com/sanjay3290/ai-skills/tree/main/skills/grok-build into .gemini/skills/grok-build/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grok-build", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install sanjay3290/ai-skills grok-buildInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add sanjay3290/ai-skills --skill grok-build -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/sanjay3290/ai-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/grok-build .github/skills/grok-build && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "grok-build" agent skill from https://github.com/sanjay3290/ai-skills/tree/main/skills/grok-build into .github/skills/grok-build/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grok-build", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sanjay3290/ai-skills --skill grok-build -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install sanjay3290/ai-skills grok-build --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sanjay3290/ai-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/grok-build .opencode/skills/grok-build && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "grok-build" agent skill from https://github.com/sanjay3290/ai-skills/tree/main/skills/grok-build into .opencode/skills/grok-build/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grok-build", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
grok-build- GitHub stars
- 432
- Token cost
- ~1.4k tokens
- SKILL.md length
- 559 words
- Files
- 2 (incl. references)
- Skills in repo
- 24
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Orchestrate coding work by delegating well-specified implementation tasks to xAI's Grok Build CLI (grok) running headlessly, while the coding assistant plans, writes the task specs, reviews every…
- Works in 2 steps: grok update --check --json — if… → grok models — if it errors or reports…
- User says: use grok
- SKILL.md covers When to delegate vs keep with…, Session preflight (once,…, Per-task loop (sequential —… and Task spec template, plus 4 more sections
- Calls git
What it does
Grok Build is an agent skill from sanjay3290/ai-skills. Orchestrate coding work by delegating well-specified implementation tasks to xAI's Grok Build CLI (grok) running headlessly, while the coding assistant plans, writes the task specs, reviews every diff, and owns the result. Use when user says: 'use grok', 'grok build', 'delegate to grok', 'have grok implement', 'have grok execute', 'have grok build', 'send to grok', 'execute this plan with grok'. Executes a Markdown implementation plan task-by-task, or ad-hoc tasks with an inline spec.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/cli.md`).
It sits in Agent Workflows, covering Planning. The repository describes itself as: 24 cross-platform agent skills for Claude Code, Cursor, Codex & Gemini CLI — databases, messaging, research, TTS, DevOps, and Google Workspace. The licence is Apache-2.0.
When your agent uses it
- User says: use grok
- Delegate to grok
- Have grok implement
- Have grok execute
Example prompts
- “use grok”
- “grok build”
- “delegate to grok”
- “/grok-build”
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- grok update --check --json — if updateAvailable is true, run grok update and
- grok models — if it errors or reports logged out, STOP and ask the user to run
What it can do on your machine
Read from SKILL.md and the folder at commit 281d88d. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Grok Build loads about 1.4k tokens when it runs, and up to ~2.4k if it reads all its reference files. Until then it costs about 125 tokens; SKILL.md has 559 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from sanjay3290/ai-skills at commit 281d88d, republished under its Apache-2.0 licence (© sanjay3290). 559 words, ~1,381 tokens.
Download SKILL.mdSave it as
.claude/skills/grok-build/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- grok-build
- description
- Orchestrate coding work by delegating well-specified implementation tasks to xAI's Grok Build CLI (grok) running headlessly, while the coding assistant plans, writes the task specs, reviews every diff, and owns the result. Use when user says: 'use grok', 'grok build', 'delegate to grok', 'have grok implement', 'have grok execute', 'have grok build', 'send to grok', 'execute this plan with grok'. Executes a Markdown implementation plan task-by-task, or ad-hoc tasks with an inline spec.
- license
- Apache-2.0
- metadata.author
- sanjay3290
- metadata.version
- 1.0
Grok Build Orchestration
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.
When to delegate vs keep with the orchestrator
| Delegate to Grok | Keep with the orchestrator |
|---|---|
| Plan tasks with clear acceptance criteria | Ambiguous requirements, architecture decisions |
| Boilerplate, scaffolding, CRUD | Deep cross-file debugging |
| Mechanical refactors | Security-sensitive code |
| Test writing from clear specs | Anything touching production infrastructure |
| UI components from mockups/specs | Tasks where writing the spec ≈ doing the work |
When in doubt, keep it with the orchestrator.
Session preflight (once, before the first dispatch)
grok update --check --json— ifupdateAvailableis true, rungrok updateand confirm withgrok --version.grok models— if it errors or reports logged out, STOP and ask the user to rungrok login.
Per-task loop (sequential — the default)
Spec. Write a self-contained task file (template below) to a temp directory OUTSIDE the target repo — the harness scratchpad if one is available, else the OS temp dir. Never write it inside the target repo. Grok has zero conversation context: no one-liner prompts, ever.
- POSIX:
mkdir -p "${TMPDIR:-/tmp}/grok-specs", then writetask.mdthere. - Windows (PowerShell):
New-Item -ItemType Directory -Force "$env:TEMP\grok-specs", then writetask.mdthere.
- POSIX:
Clean state. No uncommitted source changes — commit or stash first, so the post-run diff is exactly Grok's work. Ignore build artifacts (
__pycache__,dist/, etc.); if they show ingit status, they're usually just un-gitignored, not your concern. Never dispatch on a dirty source tree.Dispatch.
POSIX:
bash grok --prompt-file <task-file> \ --output-format json \ --always-approve \ --max-turns 30 \ --cwd <repo>Windows (PowerShell) — backtick line-continuation:
powershell grok --prompt-file <task-file> ` --output-format json ` --always-approve ` --max-turns 30 ` --cwd <repo>Parse the JSON output and save
sessionId. (--always-approveis required for headless runs —--permission-mode acceptEditssilently cancels edits with no interactive approver. Seereferences/cli.md.) For a high-stakes task, add--checkso Grok self-verifies before you review; skip it otherwise (it ~doubles latency).Review gate — non-negotiable.
- Read the diff yourself (
git diff -- <files from the spec>to skip artifact noise): does it do the task, only the task, and match repo conventions? - Run the acceptance commands from the spec.
- Pass → commit with a clear message following the repo's convention → next task.
- Fail → fix-up:
grok --resume <sessionId> -p "<specific feedback>" --always-approve --output-format json. Max 2 fix-up rounds. Still failing → revert Grok's changes (git checkout -- .;git clean -fdfor new files), do the task yourself, and tell the user Grok couldn't complete it.
- Read the diff yourself (
Show full SKILL.md (158 more words)Show less
Task spec template
# Task: <one-line title>
## Context
- Repo: <path> — <one line on what the project is>
- Conventions: <test runner, formatter, a good example file to imitate>
## Files
- Modify: <path>
- Create: <path>
## Task
<precise description of the change>
## Constraints
- Do not modify any files other than those listed above.
- <other constraints>
## Acceptance criteria
- `<exact command>` <expected result>Executing a Markdown implementation plan
- One plan task per dispatch, in order.
- Check off the plan's task checkboxes (
- [ ]→- [x]) as each task lands and passes the review gate. - If the plan explicitly marks tasks as independent, see Parallel dispatch below; otherwise stay sequential.
Parallel dispatch (opt-in exception, not the default)
Only when a plan explicitly marks tasks independent: dispatch each with
--worktree=<task-slug>, run concurrently, then review and merge one worktree at a
time through the same review gate. Merge conflicts usually eat the savings — prefer
sequential.
Failure handling
| Failure | Action |
|---|---|
stopReason: "Cancelled", empty text, no diff | Missing --always-approve — retry with it |
| CLI error / timeout | Retry once; then do the task yourself and note the fallback |
| Auth expired | Stop; ask the user to run grok login |
| 2 fix-up rounds exhausted | Revert Grok's diff; the orchestrator finishes the task |
| Dirty tree at dispatch | Refuse; commit/stash first |
Models
Default grok-4.5. Add -m grok-composer-2.5-fast only for trivial mechanical tasks.
© sanjay3290, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in skills/grok-build of sanjay3290/ai-skills.
- SKILL.md
- references/cli.md
Open the folder on GitHubat commit 281d88d
Compare with similar skills
Grok Build next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Grok Build this skillsanjay3290/ai-skills | 432 | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Executing Plans Inlineobra/superpowers | 297k | 2 repos | ~5.1k | Automated safety check: Pass | MIT | |
| Interview Meaddyosmani/agent-skills | 104k | 6 repos | ~3.8k | Automated safety check: Pass | MIT | |
| OpenSpec Guided OnboardingFission-AI/OpenSpec | 72k | 1 repos | ~4.5k | Automated safety check: Pass | MIT | |
| Writing Plansgeeksblabla/stateofdev.ma | 163 | 57 repos | ~661 | Automated safety check: Pass | None | |
| Subagent Driven DevelopmentAsvarox/allkaraoke | 261 | 37 repos | ~1.2k | Automated safety check: Pass | None |
Similar skills
Interview Me
addyosmani/agent-skills
Asks one question at a time, each with a best guess attached, until the agent is about 95 percent sure what you really want, before any plan, spec or code.
OpenSpec Guided Onboarding
Fission-AI/OpenSpec
Walks you through a complete OpenSpec workflow cycle with narration while doing real work in your codebase.
Writing Plans
geeksblabla/stateofdev.ma
A skill your agent uses when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file…
Subagent Driven Development
Asvarox/allkaraoke
A skill your agent uses when executing implementation plans with independent tasks in the current session
Planning With Files
jd-opensource/JoySafeter
Implements Manus-style file-based planning for complex tasks.
More from sanjay3290/ai-skills
All 24 skills in this repoDeep Research
sanjay3290/ai-skills
Execute autonomous multi-step research using Google Gemini Deep Research Agent.
Imagen
sanjay3290/ai-skills
Generate images using Google Gemini's image generation capabilities.
Notebooklm
sanjay3290/ai-skills
Query and manage Google NotebookLM notebooks with persistent profile auth, source sync, batch/multi queries, and structured exports.
Whatsapp
sanjay3290/ai-skills
Send and receive WhatsApp messages via the unofficial linked-device client pywhats (pip install pywhats) — pair with QR, send text/images, group chat, read receipts, presence/typing, and a…
Postgres
sanjay3290/ai-skills
Execute read-only SQL queries against multiple PostgreSQL databases.
Atlassian
sanjay3290/ai-skills
Manage Jira issues and Confluence wiki pages in Atlassian Cloud.
Related
Categories
Questions about Grok Build
What does Grok Build do?
Orchestrate coding work by delegating well-specified implementation tasks to xAI's Grok Build CLI (grok) running headlessly, while the coding assistant plans, writes the task specs, reviews every…. Grok Build is an agent skill from sanjay3290/ai-skills. Orchestrate coding work by delegating well-specified implementation tasks to xAI's Grok Build CLI (grok) running headlessly, while the coding assistant plans, writes the task specs, reviews every diff, and owns the result.
When should I use Grok Build?
Grok Build fits situations like: user says: use grok; delegate to grok; have grok implement; have grok execute.
How do I install Grok Build in Claude Code?
Run `npx skills add sanjay3290/ai-skills --skill grok-build -a claude-code`. Or copy the skill folder (skills/grok-build in sanjay3290/ai-skills) into .claude/skills/grok-build in your project. Claude Code loads it when a task matches its description.
How do I install Grok Build in Codex?
Run `npx skills add sanjay3290/ai-skills --skill grok-build -a codex`. Or copy the skill folder (skills/grok-build in sanjay3290/ai-skills) into .agents/skills/grok-build in your project. Codex loads it when a task matches its description.
Can I use Grok Build in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sanjay3290/ai-skills --skill grok-build -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/grok-build, .gemini/skills/grok-build, .github/skills/grok-build and .opencode/skills/grok-build in your project.
What does Grok Build need to run?
Going by SKILL.md and its folder, Grok Build needs the command-line tools its instructions call (git).
Does Grok Build access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Grok Build safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Grok Build use?
Grok Build is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Grok Build use?
About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.1k tokens, read only when the agent opens those files.
What are the alternatives to Grok Build?
Skills that share tags, products or a category with Grok Build: Executing Plans Inline (obra/superpowers, 297k stars), Interview Me (addyosmani/agent-skills, 104k stars), OpenSpec Guided Onboarding (Fission-AI/OpenSpec, 72k stars) and Writing Plans (geeksblabla/stateofdev.ma, 163 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Grok Build?
sanjay3290 (a GitHub user) maintains it in sanjay3290/ai-skills, which has 432 GitHub stars. The repository holds 24 skills in this directory. The repository was last updated on September 10, 2026.
Source: sanjay3290/ai-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.