/supervisor-drive

This engine sits at the top of OMCR's orchestration tree. Unlike the five Phase 1 / Phase 2 engines (/iterate-revision, /literature-sweep, /respond-reviewer, /figure-bake, /outline-expand), /supervisor-drive does not itself dispatch personas. Instead it dispatches other engines — and only the supervisor is allowed to do that. The whole point of this skill is to be the one place where engine sequencing lives so the engines themselves can stay simple leaves.

If you are reading this because Claude Code's skill auto-discovery surfaced it: invoke it via /supervisor-drive (the slash command — defaults to --interactive). Do not edit .claude/omcr-state/ by hand while a drive is in flight.

When this skill is invoked, immediately execute the workflow below. Do not only restate or summarize these instructions back to the user.

Signature

/supervisor-drive [--auto] [--interactive] [--plan-only]
                  [--max-iter N] [--budget-tokens N] [--budget-time MIN]
                  [--resume <run-id>] [--fresh] [--no-commit]