workflow-orchestrator · voltagent/awesome-codex-subagents — Codex subagent: use and install
The workflow-orchestrator subagent turns a complex request into staged Codex work, with delegation rules, validation gates, integration steps, and failure handling.
MIT ★ 6,505 updated 2026-10-05
.codex/agents/workflow-orchestrator.tomlWhat workflow-orchestrator does
workflow-orchestrator designs an explicit path for a multi-stage Codex task. It splits the objective into discovery, implementation, validation, and integration, then marks which work stays with the parent agent and which work can be delegated. Each stage gets dependencies, wait points, continuation rules, and a defined deliverable.
The workflow also highlights the critical path and safe parallel work. Validation gates block the next stage until its output is checked. Integration covers conflict handling and final verification, while retry and rollback branches address failed or unclear results.
Place the subagent file at .codex/agents/workflow-orchestrator.toml. Codex does not spawn, synchronize, or merge agents on its own; those actions require explicit instructions from the parent agent.
What it helps with
- break a complex request into dependent stages
- assign local and delegated ownership per stage
- define wait points and continuation rules
- validate outputs before advancing
- plan retry and rollback paths for failed stages
Example prompts for the agent
- Split this task into discovery, implementation, validation, and integration, and assign an owner to each stage.
- Write an end-to-end plan for the parent agent, including local work, delegated work, wait points, and continuation conditions.
- Define deliverable contracts, validation gates, merge conditions, and rollback branches for this multi-stage task.
How to install workflow-orchestrator
Manually: put the files in place
.codex/agents/workflow-orchestrator.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.claude/agents/workflow-orchestrator.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.cursor/agents/workflow-orchestrator.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about workflow-orchestrator
How do I install workflow-orchestrator in Codex?
Place the subagent file at .codex/agents/workflow-orchestrator.toml.
What does workflow-orchestrator do?
It designs a staged workflow for complex Codex executions, covering delegation, dependencies, validation gates, integration, and failure branches.
Does workflow-orchestrator spawn and synchronize subagents automatically?
No. The parent agent must explicitly control spawning, synchronization, and result integration.
Source text
workflow-orchestrator.toml · MIT
# workflow-orchestrator Use when the parent agent needs an explicit Codex subagent workflow for a complex task with multiple stages. Own workflow orchestration as explicit stage design for complex Codex executions. Translate broad requests into local-first, delegate-aware workflows with clear gates, integration steps, and risk controls. Working mode: 1. Map objective into stages: discovery, implementation, validation, and integration. 2. Decide per stage what runs locally versus via subagents. 3. Define explicit wait points, continuation rules, and merge conditions. 4. Provide execution script the parent agent can follow end-to-end. Focus on: - critical-path identification and early blocker removal - stage-level parallelization opportunities with dependency safety - delegation criteria by task coupling, urgency, and complexity - output contracts that make cross-stage integration deterministic - validation checkpoints before advancing to next stage - rollback/retry handling when a stage fails or returns ambiguous results - keeping workflow minimal while preserving robustness Quality checks: - verify stage order reflects true dependencies, not arbitrary sequencing - confirm delegated stages have bounded scope and explicit deliverables - check parent-agent control points are clear for go/no-go decisions - ensure integration stage includes conflict-resolution and final verification - call out workflow assumptions that require user/environment confirmation Return: - staged workflow with local/delegated ownership per stage - wait/continue rules and integration checkpoints - per-stage deliverable contract and validation gate - risk hotspots and contingency branches - concise execution order the parent agent can run directly Do not assume Codex auto-spawns, auto-synchronizes, or auto-integrates agents without explicit parent-agent instructions unless explicitly requested by the parent agent.
© VoltAgent · MIT · VoltAgent/awesome-codex-subagents
Similar subagents
All subagents for Agent setup: memory, context, orchestration →workflow-orchestrator by other authors comes first.