unknowns
适合项目评审与决策，能显著减少遗漏风险。
对计划/规范做盲点与高风险场景扫描，列出假设与对策。
帮你找计划或规范里没人看到的盲点和高风险场景，把隐性假设、边界失败模式和极端情况列出来并给出对策。做产品设计、规格评审或发布前检查时用它，把潜在后果和应急方案一并想清楚。特别之处是不仅报问题，还会给可执行的缓解措施，并能把结论写成 UNKNOWNS.md 供未来复用。
▸ 展开 SKILL.md 英文原文
Blind-spot hunt + war-table analysis for the current plan, spec, feature, or project — surface and ADDRESS the user's unknown knowns (tacit assumptions they carry without realizing) and unknown unknowns (edge cases, failure modes, and scenarios nobody has thought of), say plainly if anything could be BAD or backfire, think 10+ steps ahead across probable and improbable futures, and pitch cool relevant value-adding features the user didn't ask for. Every finding gets a proposed solution or mitigation, never a bare list. Can persist the result as a pseudo-oracle file (UNKNOWNS.md) so future sessions — even cheaper/weaker models — consult pre-made answers instead of rediscovering problems. Use when the user types /unknowns [topic] or /uu, or asks "what am I not seeing", "what are my blind spots", "edge cases I'm missing", "unknown unknowns", "what could go wrong", "war-table this", or wants a pre-mortem.
帮我安装这个 skill：https://raw.githubusercontent.com/fire17/claude-unknowns/main/skills/unknowns/SKILL.mdcurl -fsSL "https://raw.githubusercontent.com/fire17/claude-unknowns/main/skills/unknowns/SKILL.md"# /unknowns — blind-spot hunt & war-table oracle Surface what the user cannot see about the thing being planned or built, address every finding, and (in a project context) leave a durable pseudo-oracle behind for future models. ## Scope resolution - `/unknowns <topic>` → analyze that topic/spec/idea. - Bare `/unknowns` → analyze the active subject of this session: the plan, spec, diff, or project currently being discussed. If genuinely ambiguous, ask one short question. - `/unknowns save` (or `--save` / `--oracle`) → additionally persist the oracle file (see below). ## The analysis — four quadrants, weighted toward the last two Ground every finding in THIS specific project/spec. Gener