// Use when the workflow works but needs to handle more complex cases or produce higher-quality output through better tools, context, prompts, or models.
Use when the workflow is too slow, too expensive, or both and needs latency, cost, or token usage optimization.
Use when porting a workflow to a different AI provider, deployment environment, model tier, or organizational context.
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.
Use when workflow components are inconsistent, naming conventions vary, or a new team member's work needs alignment to project standards.
Capture a session summary — what was done, what decisions were made, and what to do next.
Use when the workflow needs multi-step processing with sequential, parallel, or conditional tool compositions and proper data flow.
| name | amplify |
| description | Use when the workflow works but needs to handle more complex cases or produce higher-quality output through better tools, context, prompts, or models. |
| argument-hint | [target area] |
| category | enhancement |
| version | 2.0.0 |
| user-invocable | true |
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 tool-orchestration reference in the agent-workflow skill for adding tools effectively.
Take a working workflow and make it more capable. Amplification adds new abilities without breaking existing functionality.
Better Prompts
Better Tools
Better Context
Better Models
| Strategy | Cost Impact | Latency Impact | Quality Impact |
|---|---|---|---|
| Better prompts | None | None | Medium-High |
| Better tools | Low | Low-Medium | High |
| Better context (RAG) | Medium | Medium | High |
| Better models | High | Medium-High | High |
After amplification, run /evaluate to verify the new capability works, or /iterate to set up quality monitoring for the enhanced workflow.
NEVER: