codex-mgmt

Delegate code writing to Codex CLI while Claude manages and reviews the workflow.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/blakegallagher1/gpc-app --skill codex-mgmt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codex-mgmt
Source: https://github.com/blakegallagher1/gpc-app/tree/main/.claude/skills/codex-mgmt
Command: npx skills add https://github.com/blakegallagher1/gpc-app --skill codex-mgmt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claude Code often needs to orchestrate software tasks without making direct edits to code. This Skill ensures that high-level planning, reviews, and coordination happen in Claude, while Codex CLI performs all implementation work, resulting in safer, faster, and more scalable software delivery.

Core Features & Use Cases

  • Architect/Plan: Claude reads code, designs changes, and validates approach before any implementation.
  • Delegated Implementation: Codex CLI executes all edits, builds, and tests according to Claude's plan.
  • Quality Assurance Gate: Claude reviews diffs, tests results, and verifications before declaring completion.

Quick Start

To begin, tell Claude: "manage codex" or "drive codex" and provide the high-level objective. Claude will outline tasks and invoke Codex CLI steps to implement, verify, and finalize. Monitor Codex CLI logs for progress, as its actions will generate diffs and test outputs. No direct code edits by Claude.

Frequently Asked Questions about codex-mgmt

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

FAQPage Schema
How do I delegate code writing to automation while managing the architecture?

Delegated implementation separates planning and review from code execution. Claude Code architects the solution and reviews changes while Codex CLI handles all edits, builds, and tests. Start by saying 'manage codex' with your high-level objective, then monitor Codex CLI logs for progress and verify outputs before completion.

Can I use CLI automation to orchestrate coding tasks without writing code directly?

Yes. This workflow uses Codex CLI as the execution layer while Claude Code manages planning, inspection, and quality assurance. Claude reads code, designs changes, and validates diffs and test results. Codex CLI implements all modifications according to the plan, enabling safer and more scalable delivery.

What's the best way to coordinate code changes across planning and implementation stages?

Separate architecture and review from implementation using a manager-executor model. Claude Code outlines tasks, reads existing code, and inspects build outputs. Codex CLI performs all edits according to the plan. This staging ensures verification gates occur before completion and reduces manual editing errors.

How do I verify builds and diffs after delegating implementation to CLI tools?

Claude Code inspects outputs using read, grep, and glob operations—never direct edits. After Codex CLI completes changes, review the diffs and test results in the logs. Declare completion only after confirming builds pass and outputs match the intended plan.

When should I use managed delegation instead of direct code editing?

Use this approach for tasks requiring high-level orchestration, quality assurance gates, or when coordinating multiple code changes. It's suited for planning-heavy workflows where review and validation must precede completion. Direct editing remains faster for small, isolated changes that don't need architectural oversight.

Does this workflow support scaling across large codebases and multi-step builds?

Yes. The manager-executor separation scales to complex projects. Claude Code handles planning and verification without direct edits while Codex CLI executes changes and builds across the full codebase. Inspection-only access via read and grep ensures safe coordination without bottlenecks.