菜单
Use when the requested result is direct evidence about local code, files, configuration, logs, tests, history, artifacts, or runtime state; do not use for external or current-source research, ordinary local reads needed during implementation, unknown-cause diagnosis, design, or mutation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when a proposed change has major external impact or the user explicitly asks to be grilled, stress-tested, questioned before action, or to save or resume a Grill discussion; do not use for ordinary clarification, settled trade-offs, mechanical details, negative intent, quoted examples, or maintenance.
Use when a failure, crash, flake, regression, or unexpected result has an unknown cause that prevents a safe fix; do not use when the cause and narrow fix are already clear, for general fact finding or design, or when the user asks only for review.
Use when the user asks to design, architect, choose an approach, or resolve a material product, workflow, API, or system trade-off before implementation and the direction is not yet settled; choose standard or adversarial search from the request and evidence; do not use for discussion-only brainstorming, external fact lookup alone, unknown-cause failures, a plan for an already chosen direction, clear implementation, or review.
Use when the user explicitly asks the host to keep working until a verifiable result, fix until green, converge without stopping, monitor through completion, or operate within a stated budget; do not use for ordinary one-shot work or infer persistence from task difficulty.
Use when the user asks to initialize, audit, repair, migrate, or slim project-local AI instructions, Teamwork context or memory, project routing, or local CodeGraph policy inside a named project; do not use for global skill, agent, policy, notification, plugin, or host installation and refresh.
Use when the user asks for an implementation plan, task breakdown, checklist, roadmap, or handoff for a direction and contract already selected, or a host requires that execution plan; do not use to brainstorm or settle product/architecture choices, research external facts, diagnose failures, review a candidate, or execute changes.
| name | teamwork-explore |
| description | Use when the requested result is direct evidence about local code, files, configuration, logs, tests, history, artifacts, or runtime state; do not use for external or current-source research, ordinary local reads needed during implementation, unknown-cause diagnosis, design, or mutation. |
Answer one local evidence question without changing the project. Explore is local-only and read-only; it does not browse the web, edit files, run destructive commands, create a standalone artifact, ask users directly, or turn an investigation into implementation. Ordinary natural discussion, brainstorming, and focused reads needed for already authorized implementation do not activate Explore.
Use Explore when the evidence question is structurally complex (multiple files, callers, definitions, or history), separable from the current task, or benefits from CodeGraph-first inspection. Ordinary single-file reads, configuration lookups, and reads that enable an already-scoped authorized change stay native.
Ordinary focused reads performed to complete an already authorized change do not activate Explore. If the remaining question is external/current, unknown-cause runtime diagnosis, an unsettled design choice, or a requested mutation, report that boundary without performing the other work.
