executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
maestro-settingsView and change Maestro toggles (terse, frontier, context-bar, discipline, verify) via the settings CLI
Independent GitHub snapshot · Automated classification · Original documentation governs
View or change Maestro settings for this project. The settings CLI manages
five primary toggles: terse, frontier, context-bar, discipline
(the optional enforcement-hook pack; off is the default), and verify
(the optional S7.3 verify-gate Stop hook; off is the default).
When the user invokes this skill, run the settings CLI from the repo root. Do not edit settings files by hand.
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:
node "<maestro-plugin-root>/settings/cli.cjs" ...
node settings/cli.cjs --help
If settings/cli.cjs is not present, use the plugin-root launcher above.
List current settings:
node settings/cli.cjs status
Set a toggle (the CLI takes a set subcommand):
node settings/cli.cjs set terse <off|lite|full|ultra>
node settings/cli.cjs set frontier <off|single:<model>|fusion:<preset>>
node settings/cli.cjs set context-bar <on|off>
node settings/cli.cjs set discipline <on|off>
node settings/cli.cjs set verify <off|warn|block>
If a subcommand name or argument differs from the above, follow the usage
printed by --help — do not guess flags.
node on PATH. A project-local Maestro install is optional when
the skill is loaded from the Maestro Codex plugin.