Menu
Use when starting a new project with Maestro or when no .maestro.md context file exists yet. Run once per project.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when the workflow is too slow, too expensive, or both and needs latency, cost, or token usage optimization.
Use when porting a workflow to a different AI provider, deployment environment, model tier, or organizational context.
Use when any Maestro command is invoked — provides foundational workflow design principles across prompt engineering, context management, tool orchestration, agent architecture, feedback loops, knowledge systems, and guardrails.
Use when the workflow works but needs to handle more complex cases or produce higher-quality output through better tools, context, prompts, or models.
Use when workflow components are inconsistent, naming conventions vary, or a new team member's work needs alignment to project standards.
Capture a session summary — what was done, what decisions were made, and what to do next.
| name | teach-maestro |
| description | Use when starting a new project with Maestro or when no .maestro.md context file exists yet. Run once per project. |
| argument-hint | [project name] |
| category | utility |
| version | 2.0.0 |
| user-invocable | true |
This is the entry point for Maestro. It creates the .maestro.md context file that all other Maestro commands depend on. No other preparation is needed — this IS the preparation.
You are conducting a structured interview to understand this project's AI workflow setup. Be conversational but thorough.
Ask these questions one section at a time. Wait for answers before proceeding.
Section 1 — Models & Providers
Section 2 — Workflow Architecture
Section 3 — Quality & Evaluation
Section 4 — Constraints
Section 5 — Priorities
After gathering all answers, generate a .maestro.md file:
# Maestro Workflow Context
Generated: [date]
## Models & Providers
[answers from section 1]
## Workflow Architecture
[answers from section 2]
## Quality & Evaluation
[answers from section 3]
## Constraints
[answers from section 4]
## Priorities
[answers from section 5, with ranked priorities]
Save this file to the project root as .maestro.md.
| Section | Status | Impact if Missing |
|---|---|---|
| Models & Providers | ? | Commands can't tailor advice to your stack |
| Workflow Architecture | ? | Commands can't assess complexity |
| Quality & Evaluation | ? | /iterate and /evaluate less effective |
| Constraints | ? | /guard and /accelerate can't set limits |
| Priorities | ? | All commands default to generic guidance |
.maestro.md file generated and savedAfter creating .maestro.md, run /diagnose for a baseline health check of your workflow.
NEVER:
.maestro.md without asking