Codex packaging

Codex CLI packaging for the agentic design reviewer. Reuses ../common/ verbatim; only the orchestration wrapper differs.

Status: implemented

Install with ./install.sh --ide codex, then in Codex ask "review my design".

How it works

Codex loads AGENTS.md from the repo root every session, so that file is kept minimal — a pointer. The actual orchestration is read on demand:

• AGENTS.md (repo root) — minimal always-on instruction telling Codex that when the user asks to review their design, it should read and follow the orchestrator. No orchestration lives here, so it doesn't bloat every session.
• .codex/design-reviewer/design-review.md — the sequential orchestrator (discover → critique → alternatives → gap → build report).

The orchestrator reads methodology from .codex/design-reviewer/methodology/*.md and shells out to .codex/design-reviewer/tools/{discover_artifacts,build_report}.py (stdlib Python, no deps).

Key difference from Claude: single agent loop, no subagents — phases run sequentially (critique → alternatives → gap), accumulating findings into one JSON payload for build_report.py. The deterministic tools and methodology are identical to every other IDE.

Source vs. install target

This codex/ folder is source (tracked). The installer writes the target (.codex/ and root AGENTS.md), which is gitignored and regenerated. If a non-ours AGENTS.md already exists at the repo root, the installer leaves it untouched and writes AGENTS.design-reviewer.md for you to merge.

install.sh --ide codex produces:

• ../common/patterns/* → .codex/design-reviewer/patterns/
• ../common/tools/* → .codex/design-reviewer/tools/
• ../common/methodology/* → .codex/design-reviewer/methodology/ ({{PATTERNS_DIR}} substituted)
• codex/design-review.md → .codex/design-reviewer/design-review.md
• common/review-config.yaml → .codex/design-reviewer/review-config.yaml
• codex/AGENTS.md → AGENTS.md (repo root; sidecar if one exists)

Usage

./install.sh --ide codex
codex   # then: "review my design"