jeo

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) JEO uses one cross-platform abstraction for orchestration: The key JEO rules are: The authoritative state is .omc/state/jeo-state.json . Hooks may help advance the workflow, but they must obey the state file. The following are commands, not descriptions. Execute them in order. Each step only proceeds after the previous one completes. If .omc/state/jeo-state.json does not exist, create it: Notify the user: "JEO activated. Phase: PLAN. Add the annotate keyword if a UI feedback loop is needed." Checkpoint recording — immediately after entering each STEP: last_error recording — on pre-flight failure or exception: Checkpoint-based resume on restart: Rule : Before exit 1 in pre-flight, always update last_error and increment retry_count .