Menu
Show the Maestro command map — a quick reference to all available skills.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Generate a bespoke issue-workflow for any target project. Phase 1 — a Claude Opus analyst reads the project deeply and produces a disposition report. Phase 2 — on approval, parallel writer agents transplant every Maestro workflow component, adapted to the target project's actual stack, test runner, dev environment, and conventions. Use when a project needs its own self-contained issue-workflow without taking a direct dependency on Maestro.
Adversarially review a grooming spec before implementation starts. Finds hidden risks, unvalidated assumptions, and missing dependencies. Standalone entry point for the challenger agent.
Run QA validation on a pull request — boots the local environment, tests acceptance criteria, and optionally posts the report as a PR comment. Standalone entry point for the qa-engineer agent.
Run a lead code review on the current branch or a given PR. Standalone entry point for the lead-reviewer agent.
Groom a single GitHub issue — produce an implementation spec and optionally post the grooming summary as a GitHub comment. Standalone entry point for the grooming-agent.
Check a change against WordPress.org plugin rules and PHPCS standards.
| name | maestro |
| description | Show the Maestro command map — a quick reference to all available skills. |
Print the following organised command reference to the user. Do not run anything else.
One baton. Any orchestra.
| Command | What it does |
|---|---|
/maestro:deliver 42 | Run the full pipeline from a GitHub issue |
/maestro:orchestrator | Jump into routing if the issue is already loaded |
| Command | What it does |
|---|---|
/maestro:groom 42 | Groom a single issue — produce a spec, optionally post the summary |
/maestro:challenge 42 | Adversarially review the grooming spec before implementation |
/maestro:review [PR] | Lead code review on the current branch or a given PR |
/maestro:qa [PR] | QA validation — boots the environment, tests acceptance criteria |
| Command | What it does |
|---|---|
/maestro:dod | Run the Definition of Done checklist |
/maestro:e2e | Run E2E smoke tests |
| Command | What it does |
|---|---|
/maestro:sprint | Plan and estimate issues for a sprint |
| Command | What it does |
|---|---|
/maestro:knowledge-graph | Map codebase dependencies |
/maestro:compliance | Check a change against WordPress.org rules |
/maestro:docs | Update developer documentation |
| Command | What it does |
|---|---|
/maestro:onboard-project | Wire a new project — writes maestro.json, scaffolds dirs |
/maestro:transplant <path> | Generate a bespoke issue-workflow for any target project |
| Plugin | Commands |
|---|---|
| Cadenza | /cadenza:changelog · /cadenza:pr · /cadenza:test · /cadenza:retrospective |
| Podium | /podium · /podium:start · /podium:status |
Type any command directly to run it. Pair with Podium for real-time observability.
