oh-my-codex

OMX product plugin entry for findings-first verification across code, plans, checks, and durable runtime state.

OMX product plugin entry for durable tmux-aware multi-worker execution with review gates and resumable state.

OMX product plugin default for routing intent through interview, planning, execution, team escalation, and verification.

Boundary-mapping mode for invasive changes, new interfaces, data contracts, and risky tradeoffs.

Durable research-mission mode for long-running discovery, optimization, and evidence gathering under .omx/.

Intent-first clarification loop for vague, risky, or product-heavy work before planning or execution.

Health-check mode for OMX install, repo state, plugin wiring, hook status, and runtime degradation.

Focused implementation mode for one planned slice with explicit verification and handoff.

Runtime-truth mode for reading tasks, sessions, reviews, inbox, memory, and team state before acting.

Execution-plan mode that turns intent into small, verifiable slices backed by durable .omx artifacts.

Evidence-first research mode for current patterns, implementation risks, and decision support.

Findings-first pre-landing review against code, plan completion, verification evidence, and durable runtime state.

Dedicated verification lane that applies the review protocol and records a durable approval or change request.

Red-green-refactor mode for behavior with clear inputs, outputs, and regression value.

Durable multi-worker orchestration with queueing, claims, inbox, review gates, and tmux-aware lifecycle control.

Execution-path mapping for entry points, data flow, side effects, and blast radius before risky work.

Default OMX flow for intent -> plan -> execute -> verify, with team escalation only when durable parallelism is justified.