@maestrofrontier/frontier 1.4.4 → 1.5.0

package/skills/maestro-frontier/SKILL.md

@@ -0,0 +1,122 @@
+---
+name: maestro-frontier
+description: Maestro Frontier local multi-CLI fusion engine - arm, disarm, inspect, or debug-run the panel
+---
+
+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
+maestro frontier mode fusion --preset frontier-trio --judge chatgpt --synth chatgpt --scope codex-project
+maestro frontier mode fusion --preset custom --models <a,b,c> --scope codex-project
+```
+
+Models: `opus` (Claude Opus 4.8, needs `claude`), `gpt-5.5` (needs `codex`),
+`gemini` (needs `gemini`). Presets: `opus-duo`, `opus-gpt`, `gpt-duo`,
+`frontier-trio`, `custom`. Friendly aliases are accepted: `chatgpt` maps to
+`gpt-5.5`, and `chatgpt-duo` maps to `gpt-duo`.
+
+Judge + synth default to Opus except for presets with explicit stage defaults.
+Override them for mixed panels with `--judge <model>` and `--synth <model>`;
+for example, `--judge chatgpt --synth chatgpt`.
+
+## 2. Show current mode/preset
+
+```bash
+maestro frontier status --scope codex-project
+```
+
+If you intentionally want one shared Codex state across unrelated repos, choose
+an explicit global name such as `--scope codex-global`. Do not use global scope
+unless that cross-repo behavior is what you want.
+
+## 3. Normal use after arming
+
+After mode is non-`off`, type ordinary Codex prompts. The trusted Codex hook
+auto-runs Frontier and injects the synthesized answer as context for the live
+reply. Turn it off with:
+
+```bash
+maestro frontier mode off --scope codex-project
+```
+
+## 4. Advanced/debug one-off run
+
+Manual one-off execution remains available for debugging:
+
+```bash
+maestro frontier run "<prompt>" --scope codex-project
+```
+
+- `off`: prints a notice, spawns nothing.
+- `single`: dispatches the one selected CLI, prints its answer.
+- `fusion`: runs the panel in parallel, then judge, then synthesizer; prints
+  the final answer (a one-line run meta goes to stderr). Report stdout verbatim.
+
+On error the engine prints `ERROR [<reason>]: <detail>` to stderr and exits
+non-zero; relay the reason.
+
+## Indicator instruction
+
+<!-- INDICATOR INSTRUCTION - apply every turn while this skill is active -->
+
+Before composing your first reply each turn, run:
+
+```bash
+maestro frontier status --scope codex-project
+```
+
+Parse the returned JSON `mode` field:
+
+- If `mode` is not `off`, make the **first line** of your reply exactly:
+  `Maestro Frontier ON (<label>)`
+  where `<label>` is formed as follows:
+  - single mode -> `single - <model>` (e.g. `single - opus`)
+  - fusion mode -> `fusion - <preset>` (e.g. `fusion - frontier-trio`);
+    for a custom preset use `fusion - custom (<model1>, <model2>, ...)`
+- If `mode` is `off`, output no indicator line.
+
+<!-- END INDICATOR INSTRUCTION -->
+
+## Notes
+
+- Real `single`/`fusion` runs spawn local CLIs and cost tokens; `off` is free.
+- The autorun hook no-ops when `FUSION_DEPTH >= 1`, so child `codex`, `claude`,
+  and `gemini` panel processes do not recursively run Frontier.
+- Each model's CLI must be on `PATH`, or point at a specific build with
+  `MAESTRO_CLAUDE_BIN` / `MAESTRO_CODEX_BIN` / `MAESTRO_GEMINI_BIN`.
+- Requires `node` on `PATH`. The bare `maestro` command is optional when the
+  skill is loaded from the Maestro Codex plugin; use the plugin-root launcher
+  above.

package/skills/maestro-settings/SKILL.md

@@ -0,0 +1,55 @@
+---
+name: maestro-settings
+description: View and change Maestro toggles (terse, frontier, context-bar) via the settings CLI
+---
+
+View or change **Maestro settings** for this project. The settings CLI manages
+the three primary toggles: `terse`, `frontier`, and `context-bar`.
+
+When the user invokes this skill, run the settings CLI from the repo root.
+Do not edit settings files by hand.
+
+## Command launcher
+
+Use `node settings/cli.cjs` when Maestro is installed in the project root. If
+that file is not present 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>/settings/cli.cjs" ...
+```
+
+## Discover available commands
+
+```bash
+node settings/cli.cjs --help
+```
+
+If `settings/cli.cjs` is not present, use the plugin-root launcher above.
+
+## Common operations
+
+List current settings:
+
+```bash
+node settings/cli.cjs
+```
+
+Set a toggle:
+
+```bash
+node settings/cli.cjs terse <off|lite|full|ultra>
+node settings/cli.cjs frontier <off|single|fusion>
+node settings/cli.cjs context-bar <on|off>
+```
+
+If a subcommand name or argument differs from the above, follow the usage
+printed by `--help` — do not guess flags.
+
+## Notes
+
+- Changes persist in Maestro's settings store and apply to subsequent agent
+  turns in this project.
+- Requires `node` on `PATH`. A project-local Maestro install is optional when
+  the skill is loaded from the Maestro Codex plugin.

package/skills/maestro-terse/SKILL.md

@@ -0,0 +1,58 @@
+---
+name: maestro-terse
+description: Toggle Maestro terse output level (lite, full, ultra, off) via the settings CLI
+---
+
+Toggle the **Maestro terse** output level for this environment. Terse mode
+condenses agent replies; levels range from `off` (default verbosity) through
+`lite`, `full`, and `ultra` (most compressed).
+
+When the user invokes this skill, run the settings CLI to read or change the
+terse level. Do not edit settings files by hand.
+
+## Command launcher
+
+Use `node settings/cli.cjs` when Maestro is installed in the project root. If
+that file is not present 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>/settings/cli.cjs" ...
+```
+
+## Check current terse level
+
+```bash
+node settings/cli.cjs --help
+```
+
+Consult the help output for the exact read subcommand, then run it. If
+`settings/cli.cjs` is not present, use the plugin-root launcher above.
+
+## Set terse level
+
+```bash
+node settings/cli.cjs terse <level>
+```
+
+Valid levels: `off` | `lite` | `full` | `ultra`
+
+Examples:
+
+```bash
+node settings/cli.cjs terse off
+node settings/cli.cjs terse lite
+node settings/cli.cjs terse full
+node settings/cli.cjs terse ultra
+```
+
+If the CLI rejects an argument or the subcommand name differs, run
+`node settings/cli.cjs --help` first and follow the printed usage.
+
+## Notes
+
+- The change persists in Maestro's settings store; it applies to subsequent
+  agent turns in this project.
+- Requires `node` on `PATH`. A project-local Maestro install is optional when
+  the skill is loaded from the Maestro Codex plugin.

package/skills/maestro-update/SKILL.md

@@ -0,0 +1,31 @@
+---
+name: maestro-update
+description: Update Maestro to the latest marketplace version for Codex
+---
+
+Update **Maestro** to the latest Codex marketplace code. This refreshes the
+configured Git marketplace and reinstalls the Maestro plugin from it.
+
+When the user invokes this skill, run:
+
+```bash
+codex plugin marketplace upgrade maestro
+codex plugin add maestro@maestro
+```
+
+The update is idempotent. It will:
+
+- Pull the latest Maestro source from the repository.
+- Refresh the installed Maestro plugin cache.
+- Refresh bundled Codex skills and hooks exposed by the plugin.
+- Leave project-local configuration (state files, secrets) untouched.
+
+## Notes
+
+- Requires the Codex CLI on `PATH`.
+- After reinstalling, restart the Codex session or open a new thread so updated
+  skills and hooks take effect.
+- If the marketplace is not configured yet, run
+  `codex plugin marketplace add mbanderas/maestro` first.
+- Portable/manual installs can still be refreshed with
+  `npx github:mbanderas/maestro install --target codex` from the project root.

package/skills/terse/SKILL.md

@@ -0,0 +1,74 @@
+---
+name: terse
+description: >
+  Token-efficient terse output mode. Cuts output tokens substantially
+  while keeping full technical accuracy. Levels: lite, full, ultra.
+  Use when the user invokes /maestro:terse, says "terse mode",
+  "be brief", or asks for less token usage.
+argument-hint: "[lite|full|ultra|off]"
+---
+
+<!-- Ported from the Caveman skill (MIT,
+github.com/JuliusBrussee/caveman) with attribution. Wenyan
+levels and the commit/review sub-modes are intentionally dropped:
+AGENTS.md S7.7 already covers terse commits/reviews — redundancy is
+token cost. This file is the single source of truth for terse-mode
+behavior; hooks/maestro-terse-mode.cjs reads and level-filters it at
+SessionStart. Keep the table-row and example-line formats intact:
+the hook filters on `| **level** |` and `- level:` prefixes. -->
+
+Respond terse. All technical substance stay. Only fluff die.
+
+## Persistence
+
+ACTIVE EVERY RESPONSE. No revert after many turns. No filler drift. Still active if unsure. Off only: "stop terse" / "normal mode" / `/maestro:terse off`.
+
+Switch: `/maestro:terse lite|full|ultra|off`.
+
+Permanent default: set `{"terseLevel": "<level>"}` in the config file
+(`%APPDATA%\maestro\config.json` on Windows;
+`$XDG_CONFIG_HOME/maestro/config.json` or `~/.config/maestro/config.json`
+on macOS/Linux). `MAESTRO_TERSE_LEVEL` env var overrides the file. The
+file is never created automatically — off until it exists.
+
+## Rules
+
+Drop: articles (a/an/the), filler (just/really/basically/actually/simply), pleasantries (sure/certainly/of course/happy to), hedging. Fragments OK. Short synonyms (big not extensive, fix not "implement a solution for"). Technical terms exact. Code blocks unchanged. Errors quoted exact.
+
+Pattern: `[thing] [action] [reason]. [next step].`
+
+Not: "Sure! I'd be happy to help you with that. The issue you're experiencing is likely caused by..."
+Yes: "Bug in auth middleware. Token expiry check use `<` not `<=`. Fix:"
+
+## Intensity
+
+| Level | What change |
+|-------|------------|
+| **lite** | No filler/hedging. Keep articles + full sentences. Professional but tight |
+| **full** | Drop articles, fragments OK, short synonyms. Classic terse |
+| **ultra** | Abbreviate (DB/auth/config/req/res/fn/impl), strip conjunctions, arrows for causality (X → Y), one word when one word enough |
+
+Example — "Why React component re-render?"
+- lite: "Your component re-renders because you create a new object reference each render. Wrap it in `useMemo`."
+- full: "New object ref each render. Inline object prop = new ref = re-render. Wrap in `useMemo`."
+- ultra: "Inline obj prop → new ref → re-render. `useMemo`."
+
+Example — "Explain database connection pooling."
+- lite: "Connection pooling reuses open connections instead of creating new ones per request. Avoids repeated handshake overhead."
+- full: "Pool reuse open DB connections. No new connection per request. Skip handshake overhead."
+- ultra: "Pool = reuse DB conn. Skip handshake → fast under load."
+
+## Auto-Clarity
+
+Drop terse for: security warnings, irreversible action confirmations, multi-step sequences where fragment order risks misread, user asks to clarify or repeats question. Resume terse after clear part done.
+
+Example — destructive op:
+> **Warning:** This will permanently delete all rows in the `users` table and cannot be undone.
+> ```sql
+> DROP TABLE users;
+> ```
+> Terse resume. Verify backup exist first.
+
+## Boundaries
+
+Code/commits/PRs: write normal. "stop terse" or "normal mode": revert. Level persist until changed or session end.

package/integrations/codex/skills/frontier/SKILL.md

@@ -1,91 +0,0 @@
----
-name: frontier
-description: Maestro Frontier local multi-CLI fusion engine — switch mode, or run a prompt through the panel
----
-
-Drive the **Maestro Frontier** engine — a zero-dependency local multi-CLI fusion
-engine (a parallel panel of local CLIs → a judge model's analysis → a grounded
-synthesis). It is the same engine the Claude Code plugin ships; here it runs
-through the `maestro` CLI with `--scope codex`.
-
-**This is a typing shortcut, not a prompt hook.** Codex has no automatic
-prompt hook, so arming a mode does **not** auto-run the engine on later prompts —
-it only persists the mode. To actually fuse a prompt, invoke `run` explicitly
-(step 3).
-
-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.
-
-## 1. Switch mode
-
-Persists to `~/.config/maestro/frontier-state.codex.json`; default `off`.
-`--scope codex` keeps Codex's armed mode independent from Claude Code, Cline,
-Cursor, and Gemini on the same machine:
-
-```bash
-maestro frontier mode off --scope codex
-maestro frontier mode single --model <model> --scope codex
-maestro frontier mode fusion --preset <preset> --scope codex
-maestro frontier mode fusion --preset custom --models <a,b,c> --scope codex
-maestro frontier mode fusion --preset <preset> --judge <model> --synth <model> --scope codex
-```
-
-Models: `opus` (Claude Opus 4.8, needs `claude`), `gpt-5.5` (needs `codex`),
-`gemini` (needs `gemini`). Presets: `opus-duo`, `opus-gpt`, `gpt-duo`,
-`frontier-trio`, `custom`. Judge + synth default to Opus; `--judge`/`--synth`
-override for any preset (e.g. `--judge opus --synth gpt-5.5`). `gpt-duo` runs
-judge + synth on GPT-5.5 — a Codex-only fusion that needs no `claude`.
-
-## 2. Show current mode/preset
-
-```bash
-maestro frontier status --scope codex
-```
-
-## 3. Run a prompt through the current mode
-
-This is the action that actually fuses, since nothing auto-runs here. Set a
-mode first (step 1), then:
-
-```bash
-maestro frontier run "<prompt>" --scope codex
-```
-
-- `off`: prints a notice, spawns nothing.
-- `single`: dispatches the one selected CLI, prints its answer.
-- `fusion`: runs the panel in parallel → judge → synthesizer; prints the final
-  answer (a one-line run meta goes to stderr). Report stdout verbatim.
-
-On error the engine prints `ERROR [<reason>]: <detail>` to stderr and exits
-non-zero — relay the reason.
-
-## Indicator instruction
-
-<!-- INDICATOR INSTRUCTION — apply every turn while this skill is active -->
-
-Before composing your first reply each turn, run:
-
-```bash
-maestro frontier status --scope codex
-```
-
-Parse the returned JSON `mode` field:
-
-- If `mode` is not `off`, make the **first line** of your reply exactly:
-  `Maestro Frontier ON (<label>)`
-  where `<label>` is formed as follows:
-  - single mode → `single · <model>` (e.g. `single · opus`)
-  - fusion mode → `fusion · <preset>` (e.g. `fusion · frontier-trio`);
-    for a custom preset use `fusion · custom (<model1>, <model2>, ...)`
-- If `mode` is `off`, output no indicator line.
-
-<!-- END INDICATOR INSTRUCTION -->
-
-## Notes
-
-- Real `single`/`fusion` runs spawn local CLIs and cost tokens; use small prompts.
-  `off` is free.
-- Each model's CLI must be on `PATH`, or point at a specific build with
-  `MAESTRO_CLAUDE_BIN` / `MAESTRO_CODEX_BIN` / `MAESTRO_GEMINI_BIN`.
-- Requires `maestro` on `PATH` (installed during Maestro setup). If it is
-  missing, install Maestro first.

package/integrations/codex/skills/update/SKILL.md

@@ -1,29 +0,0 @@
----
-name: update
-description: Update Maestro to the latest version by re-running the installer for Codex
----
-
-Update **Maestro** to the latest marketplace code. This re-runs the installer,
-which pulls the current release and overwrites the local Maestro files in place.
-
-When the user invokes this skill, run the installer from the repo root:
-
-```bash
-npx github:mbanderas/maestro install --target codex
-```
-
-The installer is idempotent — it is safe to re-run against an existing
-installation. It will:
-
-- Pull the latest Maestro source from the repository.
-- Overwrite skills, hooks, and settings scaffolding with the new versions.
-- Leave project-local configuration (state files, secrets) untouched.
-
-## Notes
-
-- Requires `node` and `npx` on `PATH`.
-- Run from the project root so the installer targets the correct directory.
-- After the installer completes, restart the Codex session (or reload the
-  project) so updated skills and hooks take effect.
-- If `npx` is unavailable, clone `https://github.com/mbanderas/maestro`
-  manually and follow the repository's install instructions.