
Maestro
Install maestro when you want Claude Code to enforce verification gates, orchestrate Codex and Gemini, and keep mission context intact across compaction.
Overview
Maestro is a plugin marketplace for the Ship phase that enforces structural thoroughness in Claude Code with verification gates, multi-model orchestration, and context persistence across compaction.
What is this marketplace?
- Verification gates that block sloppy handoffs until evidence passes
- Multi-model orchestration across Codex and Gemini alongside Claude
- Context persistence designed to survive compaction on long missions
- Mission-driven workflow with thoroughness as the default posture
- Single-plugin marketplace bundle (maestro v0.1.0) for Claude Code
Community signal: 1 GitHub stars.
What problem does it solve?
Long Claude Code missions often lose thread after compaction and ship changes without a real verification pass.
Who is it for?
Solo builders running multi-hour Claude Code missions who want enforced review steps and Codex or Gemini as extra eyes before they call work finished.
Skip if: Quick one-off prompts where you do not want orchestration overhead or mandatory verification gates.
What do I get? / Deliverables
After you register maestro, missions run with explicit gates, optional cross-model checks, and durable context so thoroughness is the default end state.
- Installed maestro plugin from the 1-plugin marketplace bundle
- Mission workflows with verification gates and optional cross-model review
Plugins in this marketplace
1 plugin — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
Canonical shelf is Ship because the plugin’s core value is structural thoroughness and verification before you treat work as done, even though you can run missions from Build onward. Review is the best fit for gates, checklist-style enforcement, and multi-model cross-checks rather than raw coding or deploy automation.
How it compares
Claude Code plugin marketplace bundle with workflow enforcement, not a single-task MCP server or a narrow integration skill.
Common Questions / FAQ
Who is Maestro for?
Maestro is for indie and solo developers using Claude Code who need mission-driven thoroughness, verification gates, and multi-model orchestration instead of ad-hoc chat.
When should I use Maestro?
Use Maestro when a Claude Code session spans compaction, touches critical code paths, or benefits from Codex or Gemini review before you merge or deploy.
How do I add Maestro to my agent?
Add the jbj338033/Maestro marketplace in Claude Code, install the bundled Maestro plugin (1 plugin, v0.1.0), then invoke it for mission workflows that expect gates and context persistence.