メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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 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.
Use when choosing whether to answer briefly, write a technical plan, perform an audit, implement code, run incremental execution, or stop for confirmation based on ambiguity, risk, reversibility, and evidence needs.
| name | systematic-investigation |
| description | 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. |
Investigar antes de corrigir. Sintoma parecido nao prova causa igual.
