codex-orchestrator

Coordinates Codex subagents with bounded ownership, compact briefs, and verified integration.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/alex-jordan547/agent-setup --skill codex-orchestrator-alex-jordan547
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codex-orchestrator
Source: https://github.com/alex-jordan547/agent-setup/tree/main/skills/codex-orchestrator
Command: npx skills add https://github.com/alex-jordan547/agent-setup --skill codex-orchestrator-alex-jordan547

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Delegating work to multiple AI subagents often leads to overlapping edits, unclear ownership, and unverified results. This Skill defines a disciplined orchestration workflow so Codex subagents receive bounded tasks, explicit file ownership, and their combined output is actually inspected and tested before acceptance. ## Core Features & Use Cases - Bounded Delegation: Assign each agent one objective, relevant source pointers, explicit file/responsibility ownership, success checks, and a stop condition. - Safe Concurrency: Use isolated worktrees when concurrent edits overlap, and ensure editing agents preserve other contributors' work. - Verified Integration: The primary agent owns integration, reconciles changes, inspects the combined diff, and runs checks against the integrated result rather than trusting completion messages. - Use Case: When a user asks to parallelize a refactor across three modules, split the work into independent briefs, run agents in isolated worktrees, then merge and run the full test suite on the combined diff. ## Quick Start Ask the agent to split this task among Codex subagents with clear ownership and verify the integrated result before committing.

Frequently Asked Questions about codex-orchestrator

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

FAQPage Schema
How do I coordinate multiple Codex subagents on one task?

Split independent work into separate briefs and keep dependent steps sequential. Give each agent one objective, source pointers, explicit file ownership, success checks, and a stop condition, then integrate and verify the combined result yourself.

How to prevent subagents from overwriting each other's changes?

Assign explicit file and responsibility ownership in each brief and instruct editing agents to preserve other contributors' work. When concurrent edits overlap, use isolated worktrees instead of sharing one working tree.

When should I delegate work to subagents versus doing it directly?

Delegate only when the user requests it or the active instructions authorize it. Independent, parallelizable tasks benefit from delegation; tightly coupled sequential steps are usually faster handled directly by the primary agent.

Can subagents create commits or pull requests on their own?

No. The primary agent owns integration and any authorized branch, commit, or PR lifecycle unless explicitly delegated. Subtasks do not inherit permission to publish their changes.

Why is a subagent's completion message not enough to accept its work?

A completion message is evidence to inspect, not proof the combined work passes. Reconcile all changes, review the integrated diff, and run checks against the merged result before accepting it.