diagnose
MANDATORY PREPARATION
Invoke /agent-workflow — it contains workflow principles, anti-patterns, and the Context Gathering Protocol. Follow the protocol before proceeding — if no workflow context exists yet, you MUST run /teach-maestro first.
Perform a systematic diagnostic scan across 5 dimensions. For each dimension, score 1-5 and provide specific findings.
Dimension 1: Prompt Quality (1-5)
Evaluate:
- Structure (4-zone pattern: role, context, instructions, output)
- Output schema definition (explicit vs. implicit)
- Instruction clarity (specific vs. vague)
- Edge case handling (addressed vs. ignored)
- Anti-patterns present (wall of text, contradictions, implicit format)
Dimension 2: Context Efficiency (1-5)
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.
147calibrate
Use when workflow components are inconsistent, naming conventions vary, or a new team member's work needs alignment to project standards.
142teach-maestro
Use when starting a new project with Maestro or when no .maestro.md context file exists yet. Run once per project.
140iterate
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