streamline
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 complexity assessment and topology simplification.
Reduce complexity without reducing capability. Every component should earn its place.
Streamlining Analysis
For each component, ask:
- Does this add measurable value? If you can't name the specific value, remove it.
- Can this be combined with another component? Merge overlapping responsibilities.
- Is this solving a real problem or an imagined one? Remove speculative complexity.
- Would a simpler alternative work? Prefer simplicity over elegance.
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.
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.
140