Ultracode for Codex: Claude-style Dynamic Workflows with a Skill

The orchestration does not happen inside one normal reply.

In a normal chat loop, the model has to keep planning, editing, checking, and summarizing in one stream. That works for small jobs. It gets messy when the task is large.

Dynamic Workflows make the work explicit:

• first plan


• then split


• then run independent parts


• then check


• then integrate

There is a cost trade-off. Anthropic warns that Dynamic Workflows can use much more than a normal Claude Code session, and the first workflow trigger asks for confirmation.

Parallel agents increase usage.

What Codex already has

Codex is different.

It does not expose Claude Code's Dynamic Workflows as a native feature. There is no official Codex ultracode mode that automatically runs the same system.

But Codex has skills.

A skill is a small instruction package. It can teach the agent how to behave for a class of tasks.

For this use case, the skill defines:

• when to keep the task direct


• when to make a plan


• when to split work


• when to use subagents


• what stays in the parent session


• how the final result gets checked

Codex can reproduce the operating procedure, not the native Claude Code implementation.

The practical mapping

The Ultracode skill uses three modes.

Direct mode is for small tasks.

Fix one typo. Read one file. Answer one narrow question. No workflow folder needed.

Workflow mode is for non-trivial work that needs a plan but does not need parallel agents.

The skill writes simple local artifacts:

.workflow/ultracode/<run-slug>/

  plan.md

  orchestration.md

  state.json

  packets/

  results/

  integration.md

  final-report.md

Delegated mode is for tasks that can be split into independent checks or edits.

When native subagent tools are available, Codex can use spawn_agent for independent work.

In practice:

• 
  explorer agents inspect code and gather facts


• 
  worker agents only edit when the write scope is clear


• the parent session integrates the result


• tests, builds, linters, or browser checks verify the final state

The parent session still owns the final answer.

Subagents produce partial results. The parent session integrates them.

Shared procedure

The shared behavior is:

• a large task gets planned


• independent work is separated


• parallelism is used only for independent work


• results are checked before integration


• verification happens at the end

This reduces one common failure mode in AI coding: a polished final answer without evidence.

The model is still capable of making mistakes. The difference is that the workflow leaves evidence: plans, separate results, integration notes, and verification output.

Implementation differences

The implementation is different.

Claude Code Dynamic Workflows are an official Claude Code feature.

Claude Code's ultracode setting is tied to Claude Code behavior.

Codex does not have that exact feature.

The Codex version is a skill. It defines how Codex should use skills, subagents, local artifacts, and verification commands.

In plain terms: Claude Code owns the native feature. Codex follows the procedure through a skill.

Prompt examples

For a normal task:

Use $ultracode to implement this feature end to end and verify it.

For a task where parallel work may help:

Use $ultracode. Use parallel agents when the task can be split, keep integration in the parent session, and verify the final patch.

That second sentence defines the delegation rule.

A skill can describe when to delegate. The current host environment still controls whether delegation is available.

Install

Codex:

mkdir -p "${CODEX_HOME:-$HOME/.codex}/skills"

cp -R ultracode "${CODEX_HOME:-$HOME/.codex}/skills/"

Claude Code:

mkdir -p "$HOME/.claude/skills"

cp -R ultracode "$HOME/.claude/skills/"

Antigravity workspace install:

mkdir -p .agents/skills

cp -R /path/to/ultracode .agents/skills/

Restart the tool after installing so it reloads the skill list.

Why there is no required Python runner

Some workflow systems use helper scripts. That can help with scaffolding or validation.

But the core of this skill is not a runner.

In Codex, subagents are launched by Codex.

In Claude Code, Dynamic Workflows are launched by Claude Code.

A portable skill should leave orchestration to the host tool.

The core file is SKILL.md.

When to use it

Good fit:

• repo-wide audits


• migrations


• feature work with discovery and tests


• security review


• risky changes that need independent checking

Bad fit:

• tiny edits


• one-file fixes


• tasks where agents would duplicate the same search


• tasks where low usage takes priority over extra checking

Rule:

Small tasks should stay small.

Large tasks should leave evidence.