compose
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. Consult the agent-architecture reference in the agent-workflow skill for topology patterns and when multi-agent is justified.
Design a multi-agent system. But first — are you sure you need one?
Step 1: Pre-Composition Check
Answer these before proceeding:
- Has a single agent been tried and failed? (If no, try single agent first)
- What specific limitation requires multiple agents? (If you can't name it, you don't need multi-agent)
- Is the cost/latency increase justified? (Multi-agent = 2-10x cost and latency)
If you can't articulate a specific limitation, use /amplify on the single agent instead.
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.
147evaluate
Use when the user wants a quality review, interaction audit, or to test the workflow against realistic scenarios.
145diagnose
Use when the user wants to find problems, audit workflow quality, or get a comprehensive health check on their AI workflow.
145calibrate
Use when workflow components are inconsistent, naming conventions vary, or a new team member's work needs alignment to project standards.
141teach-maestro
Use when starting a new project with Maestro or when no .maestro.md context file exists yet. Run once per project.
139iterate
Use when the workflow needs to self-correct, improve over time, or establish feedback loops and evaluation cycles.
139