jeo

# JEO — Integrated Agent Orchestration > Keyword: `jeo` · `annotate` · `UI-review` · `agentui (deprecated)` | Platforms: Claude Code · Codex CLI · Gemini CLI · OpenCode > > A unified skill providing fully automated orchestration flow: > Plan (ralph+plannotator) → Execute (team/bmad) → UI Feedback (agentation/annotate) → Cleanup (worktree cleanup) ## Control Layers JEO uses one cross-platform abstraction for orchestration: - `settings`: platform/runtime configuration such as Claude hooks, Codex `config.toml`, Gemini `settings.json`, MCP registration, and prompt parameters - `rules`: policy constraints that must hold on every platform - `hooks`: event callbacks that enforce those rules on each platform The key JEO rules are: - do not reopen the PLAN gate when the current plan hash already has a terminal result - only a revised plan resets `plan_gate_status` to `pending` - do not process agentation annotations before explicit submit/onSubmit opens the submit gate The authoritative state is `.omc/state/jeo-state.json`. Hooks may help advance the workflow, but they must obey the state file. --- ## 0. Agent Execution Protocol (follow immediately upon `jeo` keyword detection) > The following are commands, not descriptions. Execute them in order. Each step only proceeds after the previous one completes. ### STEP 0: State File Bootstrap (required — always first) ```bash mkdir -p .omc/state .omc/plans .omc/logs ``` If `.omc/state/jeo-state.json` does not exist, create it: ...