菜单
Use when the workflow works but needs polish, or as the final step in a diagnose → fix → refine cycle before shipping.
用 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 | refine |
| description | Use when the workflow works but needs polish, or as the final step in a diagnose → fix → refine cycle before shipping. |
| argument-hint | [target area] |
| category | fix |
| 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.
This is the final quality pass. The workflow works — now make it excellent.
Prompts
Tool Descriptions
Error Messages
Logging
Configuration
For each checklist item that fails, provide:
| Priority | Criteria | Maestro Action |
|---|---|---|
| Critical | Affects correctness or safety | /fortify or /guard before shipping |
| Important | Affects quality or maintainability | /calibrate in current cycle |
| Nice-to-have | Cosmetic or minor inconsistency | Note for next /refine pass |
After refinement is complete, run /evaluate to verify the polished workflow against realistic scenarios.
NEVER:
