Menu
Use when the user wants to tailor a workflow for a specific industry, domain, or vertical with specialized expertise, terminology, and guardrails.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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 the workflow works but needs to handle more complex cases or produce higher-quality output through better tools, context, prompts, or models.
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.
| name | specialize |
| description | Use when the user wants to tailor a workflow for a specific industry, domain, or vertical with specialized expertise, terminology, and guardrails. |
| argument-hint | [domain] |
| category | utility |
| 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.
Transform a general-purpose workflow into a domain expert.
## Generic: You are an assistant that analyzes documents.
## Specialized (legal): You are a senior legal analyst specializing in contract review.
You understand common law jurisdictions, standard contract clauses, and the
difference between representations and warranties. Always caveat that this
is not legal advice.
| Domain | Evaluation Criteria |
|---|---|
| Legal | Clause completeness, regulatory compliance, jurisdiction accuracy |
| Medical | Clinical accuracy, guideline adherence, contraindication checks |
| Financial | Calculation accuracy, regulatory disclosure, risk assessment |
| Code | Test coverage, security vulnerabilities, performance |
| Customer Support | Tone, escalation accuracy, resolution completeness |
After specialization, run /evaluate with domain-specific scenarios, then /guard to add domain-appropriate safety guardrails.
NEVER: