---
title: "maestra"
description: "Explicitly activated, context-isolated multi-agent execution with Main-owned planning and bounded review."
canonical: https://agentpluginsdirectory.com/plugins/maestra
last-updated: 2026-11-13
---

# maestra
Explicitly activated, context-isolated multi-agent execution with Main-owned planning and bounded review.
## Package we checked
The manifest we fetched is plugins/maestra/plugin.json in phni3j9a/maestra-codex-plugin. The plugin root is the directory that holds that file. Its $schema is https://agent-plugins.org/schemas/1.0.0/plugin.schema.json. The manifest lists 7 skills (doctor, finish, gate, plan, run, spec, using-maestra) and no MCP servers.
- Slug: maestra
- Publisher: Maestra contributors
- Repository: https://github.com/phni3j9a/maestra-codex-plugin
- Manifest: plugins/maestra/plugin.json
- Version: 0.3.2+codex.20260815151220
- Category (editorial): agent-tooling
- Skills: 7 (doctor, finish, gate, plan, run, spec, using-maestra)
- MCP servers: 0
- Stars: 0
- Repository created: 2026-08-16
- Repository last pushed: 2026-08-16
- Publisher type: User
- Listing: https://agentpluginsdirectory.com/plugins/maestra
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What maestra does, in the publisher's words

Maestra keeps thinking and design in Main Sol while isolating execution noise in fresh subagents.

> Installing Maestra does not change normal Codex behavior. Maestra is activated only by explicitly invoking $maestra:using-maestra.

$maestra:plan produces the complete implementation Plan in Main: architecture, Run/Task decomposition, target files/modules, implementation steps, design decisions, verification strategy, review focus, and Run gate questions. After user approval, /compact is recommended.

- $maestra:using-maestra: the only workflow entry
- $maestra:doctor
- $maestra:spec
- $maestra:plan
- $maestra:run
- $maestra:gate (normally reached automatically from run)

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/phni3j9a/maestra-codex-plugin/HEAD/plugins/maestra/README.md

## Skills

- doctor: Verify Maestra prerequisites, exact Codex multi-agent routing, Git state, and version-bound runtime configuration before execution. Use only when the user explicitly invokes $maestra:doctor. This diagnostic must not activate the Maestra workflow or modify product code.
- finish: Complete a Maestra project with risk-based final verification/review, Main Sol final semantic gate, and a user-facing report. Use only by direct explicit invocation or when Main routes here after every Run in an explicitly activated using-maestra workflow has passed its Gate.
- gate: Perform the Main Sol semantic and architectural gate after a Maestra Run or PLAN_GAP. Use only by direct explicit invocation or when Main routes here from an explicitly activated using-maestra workflow or Run. Direct invocation is for recovery/re-evaluation and does not activate the workflow.
- plan: Create the full detailed implementation plan for an approved Maestra specification in Main Sol. Use only by direct explicit invocation or when Main routes here from an explicitly activated using-maestra workflow. Main owns architecture, implementation strategy, Task decomposition, target files, and…
- run: Execute exactly one approved Maestra Run using a fresh Terra execution orchestrator. Use only by direct explicit invocation or when Main routes here from an explicitly activated using-maestra workflow. Terra may coordinate, verify, adjudicate review, and commit, but must return PLAN_GAP instead of…
- spec: Turn an already-discussed software change into a concise, user-approvable Maestra specification. Use only by direct explicit invocation or when Main routes here from an explicitly activated using-maestra workflow. Do not execute implementation work or spawn implementation agents.
- using-maestra: Activate and conduct the complete Maestra development workflow for the current task and thread. Use only when the user explicitly invokes $maestra:using-maestra; installing Maestra, ordinary development prompts, doctor, or direct phase-skill recovery must never activate this workflow.

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.
