maestro

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.

Show the Maestro command map — a quick reference to all available skills.

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.

Update developer-facing documentation to reflect code changes on the current branch.

Run the Definition of Done checklist for the current branch — PASS/WARN/FAIL with evidence.

Run E2E smoke tests (basic) or full acceptance + regression suite (extended).

Fetch a GitHub issue and run the full grooming → implementation → review → QA pipeline.

Read and refresh the project's dependency graph to trace classes, services, and modules.

Wire a new project — writes maestro.json and scaffolds the temp directory structure.

Start a full delivery run from a GitHub issue number, URL, or raw description.

Plan and estimate issues for a sprint — capacity planning, story points, HTML report.