agent-workflow
MANDATORY — Context Gathering Protocol
Before applying any workflow guidance, gather context:
-
Check for Maestro context in the project root
- First check
.maestro/context.md(v2 layout) - Then check
.maestro.md(v1 layout — backward compatible) - If it exists → read it and use the workflow context within
- If it doesn't exist → tell the user: "No workflow context found. Run /teach-maestro to set up project-specific context for better results."
- First check
-
Check for decision history (optional)
- If
.maestro/decisions.jsonlexists → read the last 5 decisions for session continuity - If it doesn't exist → proceed without it (no error)
- If
-
Minimum viable context (if no
.maestro.md):- What AI model(s) are being used?
- What is the workflow's primary task?
- Are there existing prompts, tools, or agents to work with?
- What are the quality/speed/cost priorities?
More from sharpdeveye/maestro
evaluate
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.
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