菜单
Interrogate the user relentlessly about any plan, design, spec, approach, or decision until reaching shared understanding, resolving each branch of the decision tree. Use when the user wants to stress-test, critique, pressure-test, or interrogate a plan, design, spec, or approach.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.
Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.
Start here to ship built-and-tested code to its target safely — release steps, rollout, smoke checks, and rollback.
Start here to settle how a non-trivial change will be built — interfaces, contracts, file-level structure, and trade-offs.
Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
Start here to document what shipped — READMEs, API docs, ADRs, and usage — once a feature lands or an interface changes.
| name | interrogate |
| description | Interrogate the user relentlessly about any plan, design, spec, approach, or decision until reaching shared understanding, resolving each branch of the decision tree. Use when the user wants to stress-test, critique, pressure-test, or interrogate a plan, design, spec, or approach. |
| user-invocable | true |
| metadata | {"pattern":"inversion"} |
Interrogate me relentlessly about every aspect of this plan, design, spec, or approach until we reach a shared understanding. Walk down each branch of the decision tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.
Ask the questions one at a time.
If a question can be answered by exploring the codebase, explore the codebase instead.
