메뉴
Use when the user wants to find problems, audit workflow quality, or get a comprehensive health check on their AI workflow.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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 | diagnose |
| description | Use when the user wants to find problems, audit workflow quality, or get a comprehensive health check on their AI workflow. |
| argument-hint | [target area] |
| category | analysis |
| 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.
Perform a systematic diagnostic scan across 5 dimensions. For each dimension, score 1-5 and provide specific findings.
Evaluate:
Evaluate:
Evaluate:
Evaluate:
Evaluate:
╔══════════════════════════════════════╗
║ MAESTRO DIAGNOSTIC ║
╠══════════════════════════════════════╣
║ Prompt Quality ████░ 4/5 ║
║ Context Efficiency ███░░ 3/5 ║
║ Tool Health ██░░░ 2/5 ║
║ Architecture ████░ 4/5 ║
║ Safety & Reliability ██░░░ 2/5 ║
╠══════════════════════════════════════╣
║ Overall Score: 15/25 ║
╚══════════════════════════════════════╝
CRITICAL FINDINGS:
1. [Most severe issue — immediate action needed]
2. [Second most severe]
3. [Third]
RECOMMENDED ACTIONS:
1. Run /fortify to add error handling (addresses Tool Health + Safety)
2. Run /streamline to reduce tool count (addresses Tool Health)
3. Run /refine for prompt structure improvements (addresses Prompt Quality)
Every recommended action MUST reference the specific Maestro command that addresses it. Use this mapping:
| Dimension Gap | Maestro Command | When to Recommend |
|---|---|---|
| Prompt structure, clarity, output schema | /refine | Score ≤ 4 on Prompt Quality |
| Context budget, attention gradient, memory | /streamline | Score ≤ 3 on Context Efficiency |
| Tool errors, missing tools, redundant tools | /fortify | Score ≤ 3 on Tool Health |
| Tool count reduction, unused tools | /streamline | Tool count > 7 or unused tools found |
| Safety gaps, error recovery, validation | /fortify | Score ≤ 3 on Safety & Reliability |
| Test coverage, golden tests, evaluation | /guard | No automated tests or evaluation strategy |
| Architecture boundaries, observability | /calibrate | Score ≤ 3 on Architecture Fitness |
Do NOT give generic manual actions (e.g., "Add Vitest", "Create a rollback script") without also specifying which Maestro command the user should run to implement it. The recommended action format is:
Run
/<command>to [specific action] (addresses [Dimension] #[gap number])
| Score | Meaning | Maestro Action |
|---|---|---|
| 5 | Production-excellent | No action needed |
| 4 | Good with minor gaps | /refine for polish |
| 3 | Functional but risky | /fortify or /streamline for targeted fix |
| 2 | Significant issues | /fortify + /guard — immediate attention |
| 1 | Broken or missing | /onboard-agent — rebuild required |
After diagnosis, run the command mapped to your lowest-scoring dimension. For a general improvement sequence: /fortify → /streamline → /refine.
NEVER: