菜单
Use when a user request may contain a gap between the literal ask and the real operational need, especially for refactors, fixes, audits, legacy work, risky commands, ambiguous scope, or requests where the best delivery format is not obvious.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | intent-router |
| description | Use when a user request may contain a gap between the literal ask and the real operational need, especially for refactors, fixes, audits, legacy work, risky commands, ambiguous scope, or requests where the best delivery format is not obvious. |
Antes de agir, separe pedido literal, necessidade operacional e formato de entrega.
Use when uma tarefa de alto esforco ou dificuldade precisa de um juiz robusto e contraparte adversarial antes de concluir.
Use when delegating bounded subtasks to another agent or lighter model through Codex CLI, Hermes CLI, Antigravity CLI, or a local orchestration script to save tokens without losing control of scope and evidence.
Use when a task depends on library, framework, SDK, API, CLI, cloud service, version-specific behavior, setup instructions, migration guidance, or any external documentation that may be stale or mutable.
Use when debugging panes, errors, anomalies, regressions, flaky behavior, broken tests, incidents, unexpected UI behavior, or any failure where jumping straight to a fix could hide the real cause.
Use when a task changes UI, layout, frontend behavior, browser interaction, screenshots, visual regressions, E2E flows, accessibility-visible states, or anything that must be inspected in a browser.
Use when delivering a high-risk plan, architecture, audit, migration, security conclusion, refactor strategy, or any non-obvious technical recommendation that could be wrong in costly ways.
