codex-grok

Delegates frozen implementation plans from a Codex session to Grok CLI for execution and verification.

4|Updated Jun 2, 2026
One-click install
npx skills add https://github.com/sukbearai/king-ai --skill codex-grok-sukbearai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codex-grok
Source: https://github.com/sukbearai/king-ai/tree/main/packages/skills/skills/codex-grok
Command: npx skills add https://github.com/sukbearai/king-ai --skill codex-grok-sukbearai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Non-trivial implementation work in a Codex session often needs a separate execution pass, but handing an unresolved plan to another agent causes scope creep and redesign. This Skill enforces a strict workflow where Codex freezes the plan, Grok CLI executes it, and Codex reviews and verifies the result. ## Core Features & Use Cases - Session Gate: Applies only inside a Codex session and explicitly forbids nested Codex invocations, keeping planning in the coordinator. - Frozen Plan Contract: Requires the plan to specify files, ordered steps, exact verification commands, and risks before delegation. - Grok Execution & Follow-Up: Provides ready prompt-file templates for initial execution and narrow follow-up fixes, with a two-round failure limit before the coordinator takes over. - Use Case: You have a refactor with a known outcome but an unclear file-level path. Freeze the plan in Codex, delegate execution to Grok CLI with grok --prompt-file, then review the diff and run the tests yourself. ## Quick Start In a Codex session, ask the agent to use the codex-grok workflow to freeze your implementation plan and delegate execution to Grok CLI.

Frequently Asked Questions about codex-grok

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I delegate code implementation from Codex to Grok CLI?▼

Freeze a complete plan in the Codex session covering files, ordered steps, and verification commands, then pass it to Grok via a prompt file using grok --prompt-file with --cwd and --output-format plain. Review the diff and run tests in Codex afterward.

When should I use a Codex-plus-Grok delegation workflow?▼

Use it for non-trivial implementation where the desired outcome is known but the exact file-level execution path is not frozen, such as refactors, bug fixes, or migrations. Skip it for tiny edits, design-only work, or one-pass investigations.

Can this workflow run outside a Codex session?▼

No. The session gate stops the workflow in any non-Codex harness, and explicitly naming the skill does not override the gate. It also forbids nested Codex invocations such as codex exec.

What happens when Grok execution fails or produces a bad result?▼

If the plan was bad, fix it in the Codex session first; if execution was faulty, send Grok a narrow follow-up with the exact failure proof using --continue. After two failed rounds, stop delegating and finish the work in the coordinator.

What must a frozen implementation plan contain before delegation?▼

The plan must include problem framing and non-goals, exact files or modules to change, ordered implementation steps, exact tests and verification commands, and risks. Unresolved alternatives should not be handed to Grok unless choosing among them is the task.