devils-advocate
Structurally pressure-test a thesis (devil's advocate): decomposes the thesis into explicit claims and implicit assumptions (numbered A1/A2), systematically retrieves counter-arguments with direct citations from user-provided evidence, assigns High/Medium/Low risk flags, complements with base-rate outside views, and provides a list of "monitorable falsification signals"; delivers a dual-layer output of structured findings + human-readable narrative report. If no counter-evidence is found, honestly states "Not found" without fabrication. Replicated from LinqAlpha's (hedge fund AI product) public Devil's Advocate architecture, layered with CIA Structured Analytic Techniques and RAND Assumption-Based Planning. Use this skill when the user wants to "pressure test / play devil's advocate / find blind spots / break down assumptions / challenge this thesis / build a bear case / red-team this proposal / review before the Investment Committee / pressure test my thesis", or brings an investment thesis, IC memo, research conclusion, or business decision to be critiqued—even if they do not explicitly say "devil's advocate".
1How It Works & Mechanism
Methodologically replicates the production prompt/schema publicly shared by LinqAlpha (hedge fund AI product) for Devil's Advocate, layered with techniques such as CIA Key Assumptions Check, ACH, and RAND ABP; replicated sources are stored verbatim in reference.
> "Devil's Advocate is an AI research agent purpose-built to help investors systematically > pressure-test their investment theses using their own trusted sources at 5–10 times the > speed of traditional review."
The first layer of mechanism explicitly establishes the contrarian persona: since default LLMs tend to flatter the user (RLHF sycophancy), playing devil's advocate must be an explicitly assigned role-based workflow anchored strictly to evidence materials, prohibiting ungrounded nitpicking.
所以反方角色必须被显式赋予,不能指望模型自发唱反调。
Assumption decomposition engine: breaks down the thesis into explicit claims and implicit assumptions (numbered A1/A2), tagged with type (factual/predictive/mechanistic) and load-bearing weight; low-load assumptions are deprioritized and skipped during retrieval; assumption enumeration has no upper limit, while only retrieved items are bounded.
**隐性假设**(implicit assumptions):没写出来、但论点要成立就必须为真的前提。这一类才是盲点的主产区——确认偏误让人看不见自己依赖了什么。
Counter-evidence retrieval with built-in two-prong questioning and source hierarchy: directly undermining/contradictory materials + ACH-style 'expected-but-absent' evidence; evidence credibility prioritizes official filings > expert calls > broker research > tier-1 media > social media aggregations.
**如果这条假设为真,材料里本应看到、却没看到的证据是什么?**(ACH 的核心一问——缺席的证据也是证据)
Dual-layer artifact delivery: audit layer da_findings.json (structured findings, top-level object to accommodate coverage statements) and human-readable layer da_report.md (thematically grouped narrative + [n] inline citation indices + three lists: References, Surviving Assumptions, Coverage).
默认写入当前工作目录的 `da_findings.json`(用户指定了位置则用用户的;供程序处理与复核)。顶层是一个**对象**而不是裸数组——覆盖面声明要有处安放
Built-in anti-inflation and honesty guardrails: risk_flag evaluates counter-evidence lethality rather than probability; if over half are High, ranking and calibration must be re-evaluated; if no counter-evidence is found, states 'No counter-evidence found in the provided materials' (≠ assumption holds); bias in materials must be explicitly noted in the report.
若超过半数条目被判 High,先把全部条目按杀伤力互相排序再重新定档——全是 High 等于没有分级(首次实测第一版就判出了 6/8 个 High)。
2Core Capabilities
4Recommended Governance & Evidence
- 本地工作目录: File read/write and artifact output: da_findings.json (current working directory; user can specify alternate path)
5Second-Pass Verification
- [ok] 复刻出处(LinqAlpha + AWS 博客)真实存在 — references/linqalpha_reference_implementation.md 收录 AWS ML Blog 2026-02-11 URL、原厂四步流程与生产 prompt 模板;SKILL.md 设计依据表同时列出 CIA/RAND/DEBATE 等来源,无虚构引用。
- [ok] 『每条反方论证必须带引用 + 逐字摘录』红线 — SKILL.md Step 2 硬规则逐字存在(含省略号/禁改写的细节);Step 2 置空规则(找不到写『未在给定材料中找到反证』)同在。
- [ok] 双层产物(da_findings.json 审计层 + da_report.md 人读层) — Step 3 与 Step 4 均声明默认写入当前工作目录;fan-out 子代理落盘 da_findings_A<编号>.json 的路径规则也在 Step 3。
- [ok] 无脚本/无网络/无凭证(安全结论基础) — 目录仅 SKILL.md + 2 references;全目录扫描无执行/网络/凭证代码;'citations' 字段指向材料文件/URL 而非任何运行时网络调用。
- [ok] risk_flag 三档锚定 + 防膨胀规则 — 三档定义(High=核心结论不再成立 / Medium=幅度或时间表折损 / Low=边际修正)与『超半数 High 重新排序定档』原文均在。
- [ok] base_rate 诚实边界(禁止另起检索/编造) — 『只在给定材料内能构建参考类时填写…禁止编一个基础比率,也不为此另起检索』原文存在,防止模型外搜破坏检验边界。
- [ok] 功能声明 vs 实际能力夸大检查 — description 声称的能力(拆假设、逐条检索带出处反证、风险分级、base_rate、信号标、双层输出、不编造)逐项有对应 Step/红线实现;未声称自动联网检索或判断论点对错。
- [ok] 元数据(commit/license/stars) — 本地 HEAD == pin d5c4678cb5d4fd6acc9c922690df035dbd33d247;GitHub API:MIT、stars 1385(2026-09-09 实采)、pushed_at 2026-09-09T12:33:29Z。
6Verdict & Scenarios
fafd917ff4bed4b2…