omc-configlisted

# /omc-config — guided oh-my-claude configuration This skill walks the user through oh-my-claude's runtime flags using `AskUserQuestion` so they never have to type values or grep `~/.claude/oh-my-claude.conf` manually. It auto-detects three modes: - **setup** — first time through the skill (post-install, no `omc_config_completed=` sentinel yet) - **update** — bundle version is newer than `installed_version` (after `git pull && bash install.sh`) - **change** — already configured; user wants to inspect or adjust The user can override detection by passing `setup`, `update`, or `change` as the argument. The skill writes ONLY to `oh-my-claude.conf`. It does not edit `settings.json` (that's the harness's job at install time) or session state. It can trigger two side effects when the user opts in: rewriting agent model assignments via `switch-tier.sh`, and registering the watchdog scheduler via `install-resume-watchdog.sh`. --- ## Step 1 — Detect mode and show current state Run mode detection: ```bash bash ~/.claude/skills/autowork/scripts/omc-config.sh detect-mode ``` Possible outputs: - `not-installed` — `~/.claude/oh-my-claude.conf` is missing or has no `installed_version`. Tell the user to run `install.sh` first (or follow `AGENTS.md` § "Agent Install Protocol") and stop. Do not proceed. - `setup` — first-time framing. - `update` — upgrade framing. - `change` — ad-hoc framing. If the user passed an argument (`setup`, `update`, or `change`), use that instead of the det