maestro-frontierlisted

Drive the **Maestro Frontier** engine: a zero-dependency local multi-CLI fusion engine where a parallel panel of local CLIs feeds a judge model's analysis and a grounded synthesis. When the Maestro Codex plugin hook is installed, enabled, and trusted, arming a non-`off` mode makes normal later Codex prompts auto-run through Frontier until you turn it off. Users should not need to type `maestro frontier run "<prompt>"` for normal use. Map the user's request to one engine CLI call and run it from the repo root. Do not edit the engine's state file by hand. ## Command launcher Use `maestro` when it is on `PATH`. If it is not, and this skill is loaded from the Maestro Codex plugin, locate the plugin root by walking up from this `SKILL.md` until `.codex-plugin/plugin.json` is present, then run: ```bash node "<maestro-plugin-root>/bin/maestro.cjs" frontier ... ``` In the examples below, `maestro frontier ...` means either the bare command or that plugin-root `node .../bin/maestro.cjs frontier ...` form. ## 1. Switch mode Project/workspace scope is the default recommendation. Use `--scope codex-project` from the repository root; the CLI expands it to the same `codex-<8hex>` workspace scope the Codex plugin hook resolves from `PLUGIN_ROOT` / `PLUGIN_DATA`. Default mode is `off`. ```bash maestro frontier mode off --scope codex-project maestro frontier mode single --model <model> --scope codex-project maestro frontier mode fusion --preset chatgpt-duo --scope codex-project maest