sharpdeveye/maestro

accelerate

Use when the workflow is too slow, too expensive, or both and needs latency, cost, or token usage optimization.

원문 언어: 영어

adapt-workflow

Use when porting a workflow to a different AI provider, deployment environment, model tier, or organizational context.

원문 언어: 영어

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.

원문 언어: 영어

amplify

Use when the workflow works but needs to handle more complex cases or produce higher-quality output through better tools, context, prompts, or models.

원문 언어: 영어

calibrate

Use when workflow components are inconsistent, naming conventions vary, or a new team member's work needs alignment to project standards.

원문 언어: 영어

capture

Capture a session summary — what was done, what decisions were made, and what to do next.

원문 언어: 영어

chain

Use when the workflow needs multi-step processing with sequential, parallel, or conditional tool compositions and proper data flow.

원문 언어: 영어

compose

Use when a single agent demonstrably cannot handle the task and multi-agent coordination is justified.

원문 언어: 영어

diagnose

Use when the user wants to find problems, audit workflow quality, or get a comprehensive health check on their AI workflow.

원문 언어: 영어

enrich

Use when the agent needs access to information beyond its training data — knowledge sources, RAG pipelines, or grounding data.

원문 언어: 영어

evaluate

Use when the user wants a quality review, interaction audit, or to test the workflow against realistic scenarios.

원문 언어: 영어

extract-pattern

Use when the user wants to create templates, extract reusable patterns, document solutions, or build a pattern library from working workflows.

원문 언어: 영어

fortify

Use when the workflow lacks error handling, has been failing in production, or needs retry logic, fallback strategies, and circuit breakers.

원문 언어: 영어

guard

Use when deploying to production, handling sensitive data, or the workflow needs safety constraints, input validation, and security boundaries.

원문 언어: 영어

iterate

Use when the workflow needs to self-correct, improve over time, or establish feedback loops and evaluation cycles.

원문 언어: 영어

onboard-agent

Use when starting a new project, adding a new agent to an existing system, or setting up workflow infrastructure from scratch.

원문 언어: 영어

recap

Quick summary of the last session — commands run, files changed, and what to do next.

원문 언어: 영어

refine

Use when the workflow works but needs polish, or as the final step in a diagnose → fix → refine cycle before shipping.

원문 언어: 영어

reflect

Analyze command history to identify which skills work, which fail, and where to improve.

원문 언어: 영어

specialize

Use when the user wants to tailor a workflow for a specific industry, domain, or vertical with specialized expertise, terminology, and guardrails.

원문 언어: 영어

streamline

Use when the workflow feels too complex, has accumulated cruft, or has redundant steps and overlapping tools that need consolidation.

원문 언어: 영어

teach-maestro

Use when starting a new project with Maestro or when no .maestro.md context file exists yet. Run once per project.

원문 언어: 영어

temper

Use when the workflow feels over-engineered, has premature optimizations, unnecessary abstraction layers, or complexity beyond actual requirements.

원문 언어: 영어

turbocharge

Use when the user wants to push past conventional workflow limits with advanced performance techniques like parallel orchestration, streaming pipelines, or adaptive routing.

원문 언어: 영어

zero-defect

Use when you need maximum precision on a critical task — production deployments, security-sensitive code, financial calculations, or any work where mistakes are unacceptable.

원문 언어: 영어