phni3j9a/maestra
Explicitly activated, context-isolated multi-agent execution with Main-owned planning and bounded review.
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.
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.
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.
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 verification strategy; Terra must not fill planning gaps.
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 making missing design decisions.
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.
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.