maestro

███╗   ███╗ █████╗ ███████╗███████╗████████╗██████╗  ██████╗
████╗ ████║██╔══██╗██╔════╝██╔════╝╚══██╔══╝██╔══██╗██╔═══██╗
██╔████╔██║███████║█████╗  ███████╗   ██║   ██████╔╝██║   ██║
██║╚██╔╝██║██╔══██║██╔══╝  ╚════██║   ██║   ██╔══██╗██║   ██║
██║ ╚═╝ ██║██║  ██║███████╗███████║   ██║   ██║  ██║╚██████╔╝
╚═╝     ╚═╝╚═╝  ╚═╝╚══════╝╚══════╝   ╚═╝   ╚═╝  ╚═╝ ╚═════╝

What Is Maestro?

Maestro is a Claude Code plugin that conducts a complete, production-grade AI delivery pipeline for any project.

Install it once. Wire it to your repo in two minutes. Then watch twelve specialised agents pick up a GitHub issue, write the spec, implement the code, open the PR, and self-correct — all from a single command.

/issue-workflow 42

No prompt engineering. No agent babysitting. No score that drifts out of sync across repos.

Install

/plugin marketplace add wp-media/claude-marketplace
/plugin install maestro@wp-media

Then wire your project:

/maestro:onboard-project

That's it. The pipeline is active.

The Pipeline

Every run follows the same path — from issue to ready-to-review PR:

flowchart TD
    A[📋 GitHub Issue] --> B[issue-workflow]
    B --> C[🎼 Orchestrator]

    C --> D[🔍 Grooming Agent]
    D --> E{Risk & Effort?}

    E -->|Medium / High| F[⚔️ Challenger]
    E -->|Low| G

    F --> G[🌿 Branch + Task Graph]
    G --> H{Domains?}

    H -->|Backend| I[⚙️ Backend Agent]
    H -->|Frontend| J[🎨 Frontend Agent]
    H -->|Both| K[⚙️ + 🎨 Parallel]

    I & J & K --> L[🚀 Release Agent]
    L --> M[Open Draft PR]

    M --> N[📋 DOD L2]
    M --> O[👀 Lead Reviewer]
    M --> P[🧪 QA Engineer]

    N & O & P --> Q{All gates pass?}
    Q -->|Yes| R[✅ PR Ready for Review]
    Q -->|No| S[🔁 Fix Loop]
    S --> O

The Agents

Twelve specialists. Each one has a single job.

One Score, Any Ensemble

Every agent reads a single config file — .claude/maestro.json — committed in your repo. The score is the same. Only the ensemble changes.

Without Maestro                    With Maestro
─────────────────────              ──────────────────────────────
project-a/                         Maestro plugin (installed once)
  .claude/agents/ ──┐                agents/        ← one score, always current
  .claude/skills/ ──┤                skills/        ← one score, always current
     (drifting)    │
                   │              project-a/
project-b/         │                .claude/maestro.json   ← ensemble identity
  .claude/agents/ ──┤
  .claude/skills/ ──┤              project-b/
   (older, drifted) │                .claude/maestro.json   ← ensemble identity
                   │
project-c/         │              project-c/
  .claude/agents/ ──┘                .claude/maestro.json   ← ensemble identity
  (oldest, most diverged)

Updates are automatic. When Maestro ships a new movement, every ensemble picks it up on the next Claude session — no action needed.

Config

One file, everything tunable:

{
  "ai": {
    "slug":               "my-plugin",
    "display_name":       "My Plugin",
    "repo":               "my-org/my-plugin",
    "temp_root":          ".maestro",
    "base_branch":        "origin/develop",
    "architecture_skill": "my-plugin-architecture",
    "frontend_skill":     null,
    "editions":           null,
    "e2e": {
      "settings_path":    null,
      "ci_integration":   false,
      "license_option_key": null
    }
  }
}