teach-maestro
BOOTSTRAP — First Command to Run
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.
Interview Questions
Ask these questions one section at a time. Wait for answers before proceeding.
Section 1 — Models & Providers
- What AI model(s) are you using? (e.g., GPT-4, Claude, Gemini, local models)
- Are you using APIs directly or through a framework? (e.g., LangChain, LlamaIndex, custom)
- What are your context window sizes?
Section 2 — Workflow Architecture
More from sharpdeveye/maestro
agent-workflow
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.
149evaluate
Use when the user wants a quality review, interaction audit, or to test the workflow against realistic scenarios.
147diagnose
Use when the user wants to find problems, audit workflow quality, or get a comprehensive health check on their AI workflow.
147calibrate
Use when workflow components are inconsistent, naming conventions vary, or a new team member's work needs alignment to project standards.
142iterate
Use when the workflow needs to self-correct, improve over time, or establish feedback loops and evaluation cycles.
140fortify
Use when the workflow lacks error handling, has been failing in production, or needs retry logic, fallback strategies, and circuit breakers.
140