Skip to main content

orchestrated-codex

A standalone, Codex-native software delivery workflow. It installs a reusable orchestration skill and focused custom agents so Codex follows a structured process for discovery, planning, independent plan review, implementation, testing, and final review. The skill instructs the primary Codex thread to orchestrate only — classify the request, delegate every unit of work to a named subagent or the built-in worker, and verify the result. The orchestrator hands each subagent a scoped digest of the plan and a discovery impact map so work proceeds without re-reading whole artifacts, keeping runs fast and cheap under the same phased contract.

Installation

Install with uv:

uvx orchestrated-codex --install

To run from source instead, use a checkout:

git clone https://github.com/knuthelge/orchestrated-codex.git
cd orchestrated-codex
uv run main.py --install

Restart Codex or start a new conversation after installation. To use the workflow, invoke it explicitly with $orchestrated-delivery; Codex will not select it automatically based on the request.

The installer writes to two independent roots:

  • The skill installs under $HOME/.agents/skills/orchestrated-delivery, a documented Codex skills root, so Codex discovers it.
  • The agents install under the Codex home — CODEX_HOME when it is set and ~/.codex otherwise — as agents/*.toml.

Use --codex-home PATH to target another Codex home for the agents; the skill always resolves under $HOME/.agents/skills.

Uninstall

Remove the installed files with:

uvx orchestrated-codex --uninstall

The installer refuses to overwrite files it does not own. Uninstall removes only installed files that still match the recorded hashes across both roots and then deletes the manifest; locally modified installed files are preserved and reported.

Installed components

  • orchestrated-delivery (skill): task classification and an adaptive discovery, planning, independent plan review, implementation, testing, and final-review workflow. Installs under $HOME/.agents/skills.
  • agents/discovery.toml: read-only codebase reconnaissance.
  • agents/spec-designer.toml: requirements and technical design.
  • agents/rubber-duck.toml: independent PRD peer review (PASS/CONCERNS).
  • agents/ui-designer.toml: visual design specification for substantial UI work.
  • agents/tester.toml: authors and runs tests and verifies requirements (PASS/FAIL).
  • agents/final-reviewer.toml: read-only holistic final review.

Implementation is delegated to Codex's built-in worker. The primary Codex thread orchestrates the workflow and does not implement work itself.

Development

Run from a checkout and execute the tests:

uv run main.py --install --codex-home /path/to/test-home
uv run python -m unittest discover -s tests

Build the wheel and source distribution and inspect them:

uv build

The PyPI distribution and command are both named orchestrated-codex. The importable Python module remains codex_orchestrator for compatibility.

Metadata

Release files for orchestrated-codex 0.1.5

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for orchestrated-codex 0.1.5
File Size Uploaded
orchestrated_codex-0.1.5.tar.gz 12.7 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for orchestrated-codex 0.1.5
File Interpreter ABI Platform
orchestrated_codex-0.1.5-py3-none-any.whl Python 3 none any Details

Total release size: 32.2 kB

Release files / orchestrated_codex-0.1.5.tar.gz

Download URL orchestrated_codex-0.1.5.tar.gz
Size 12.7 kB
Tags Source
SHA-256 checksum
How to use checksums
8ed878f3208baf25925fc3032b94d46712b121b2a341d4ae2a73b90d72937d88
BLAKE2b-256 checksum
How to use checksums
374f85d2152016338c2c0ba5a03d83305879581ef8a3cee7e49fa23198416e6c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 3, 2026.

Transparency log

Release files / orchestrated_codex-0.1.5-py3-none-any.whl

Download URL orchestrated_codex-0.1.5-py3-none-any.whl
Size 19.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
5e34feff9e4a9eaac1828ffdce3c012f33f27b8ded94339ea825723c41f1b07d
BLAKE2b-256 checksum
How to use checksums
68ec5812bb07c5734cfcacc752739263ef347d21aa700a2db456ace5fe4c8315
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 3, 2026.

Transparency log

Release history Release notifications | RSS feed

0.1.13

2 release files

0.1.12

2 release files

0.1.10

2 release files

0.1.9

2 release files

0.1.8

2 release files

0.1.7

2 release files

0.1.6

2 release files

This release

0.1.5 This release

2 release files

0.1.4

2 release files

0.1.3

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page