菜单
Use when a spec, plan, design, or idea needs adversarial review to find what's wrong rather than what's right. Triggers include "poke holes in this", "tear this apart", "what am I missing", "stress test this", "find what's wrong", "challenge this", and "what could go wrong".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when checking whether field-guide reference pages still match current code and tests. Reads pages plus fg-evidence anchors, reports or fixes semantic drift, and can use sub-agents for parallel audit batches. Triggers include "resolve drift", "semantic drift", "check accuracy", "verify the reference against code", and "audit the wiki".
Use after ingesting or editing field-guide pages to attach living code/test anchors. Adds or refreshes fg-evidence metadata without trying to prove prose accuracy. Triggers include "update evidence", "wire evidence", "add evidence anchors", and "connect the wiki to code".
Use when extracting knowledge from .lore/ artifacts into the reference wiki. Converts work artifacts (retros, specs, plans, research, notes) into structured wiki pages grouped by knowledge type. Reads Markdown or HTML sources and writes Markdown by default. Triggers include "ingest this", "extract knowledge from", "add this to the wiki", "update the reference from", and "populate the field guide".
Use when setting up field-guide on a project for the first time, or to refresh the scheduled lint job after it expires. Triggers include "init field-guide", "set up field-guide", "refresh field-guide lint schedule", and "bootstrap the wiki".
This skill is used when the project wiki needs a health check. Triggers include 'lint the wiki', 'check wiki health', 'run field-guide lint', 'are there stale wiki pages', 'find orphaned pages', 'check for contradictions in the wiki'.
Use when asking questions about the project wiki, querying accumulated knowledge, searching project decisions or lessons. Triggers include "query the wiki", "what does the wiki say about", "search project knowledge", and natural language questions directed at the field-guide wiki.
| name | poke-holes |
| description | Use when a spec, plan, design, or idea needs adversarial review to find what's wrong rather than what's right. Triggers include "poke holes in this", "tear this apart", "what am I missing", "stress test this", "find what's wrong", "challenge this", and "what could go wrong". |
Shift to adversarial posture. Find what's wrong, not what's right.
No artifacts produced. This is a posture, not a process.
Break things to first principles before rebuilding. Separate facts from interpretations from assumptions. Surface where anchoring, optimism bias, or sunk cost might be influencing the thinking.
Ask one question at a time. Build on responses. Push on weak spots. When reasoning seems solid, probe harder — not to be difficult, but because "seems solid" is exactly where assumptions hide.
When the same defense repeats, move to a different angle or offer to stop. When nothing new is emerging, synthesize what shifted and offer an exit.
This produces no files, no plans, no delegated agents. Just sharper thinking.
