Maestro Install

One-time setup of Maestro for a project: lay down the orchestrator scaffolding, then open the visual editor to author the config. The heavy lifting of the config itself (form → maestro.json → render → rules) is delegated to the /maestro-app skill, so this skill only does the parts /maestro-app can't: detecting the project's implementation agent(s) and scaffolding the orchestrator the editor needs.

maestro-install:  analyze repo → offer local skills → scaffold orchestrator → run /maestro-app (form + write + render + rules) → report
              (impl agents)   (best-fit + consent)                         └── /maestro-app needs maestro.md to exist; the scaffold step creates it

User's intention

$ARGUMENTS

Workflow