用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/yogsoth-ai/de-anthropocentric-research-engine --skill deductive-hypothesis-generation命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
Strategy: Dialectic engine retuned for truth-seeking, not survival. A defender steelmans a claim into its MOST falsifiable form, a critic attacks to refute it, a judge classifies the exchange into BROKEN/CORROBORATED/UNFALSIFIABLE — the judge does NOT pick a winner or score persuasiveness. Methods: Irving debate (repurposed), Toulmin argumentation, Mayo severe testing.
Campaign: Logical extreme and boundary testing via reductio ad absurdum and edge-case analysis. Core question: Does this artifact collapse under logical limits and boundary conditions? Methods: Lakatos 1976, Dutilh Novaes 2016, BVA, Flyvbjerg Critical Case, Popper.
Campaign for mapping argument structures — extract claims, link evidence, assess strength, synthesize positions. Produces argument graphs in the wiki vault.
基于 SOC 职业分类
正在显示 SKILL.md
| name | deductive-hypothesis-generation |
| description | Strategy: deduce hypotheses from existing theory |
| version | 1.0.0 |
| category | hypothesis-formation |
| type | strategy |
| campaign | hypothesis-formulation |
| tactics | ["theory-mechanism-extraction","falsifiability-audit"] |
| sops | ["theory-identification","mechanism-extraction","variable-identification","relationship-specification","boundary-condition-specification","falsifiability-check","operationalization"] |
| dependencies | {"tactics":["falsifiability-audit","theory-mechanism-extraction"]} |
Deduce hypotheses from existing theory: in domains with mature theory, transform theoretical propositions into specific testable predictions through an explicit reasoning chain.
Not applicable: emerging domains rich in data but lacking theory → use inductive-hypothesis-generation instead.
Theory → Mechanism → Variable Relationship → Testable Prediction
The core logic of deduction:
Every step must be traceable: each prediction traces back to a mechanism, each mechanism traces back to a theory. This is what distinguishes a deductive hypothesis from a guess.
Common pitfalls:
| Tier | Theory coverage | Mechanism extraction | Hypothesis output | Falsifiability |
|---|---|---|---|---|
| S | ≥2 named theories | ≥3 causal mechanisms | ≥2 structured hypotheses | 1 falsification scenario per hypothesis |
| M | ≥3 named theories | ≥5 causal mechanisms | ≥3 structured hypotheses | ≥1 scenario + boundary conditions per hypothesis |
| L | ≥5 named theories | ≥8 causal mechanisms | ≥5 structured hypotheses | full falsifiability audit + competing-theory comparison |
theory-identification SOP: scan the domain literature and list the named theories relevant to the gap and their core propositionsmechanism-extraction SOP (via the theory-mechanism-extraction tactic): extract causal mechanism chains from each theoryvariable-identification SOP: translate the constructs in the mechanisms into operational variablesrelationship-specification SOP: specify directional relationships among variables (including moderating/mediating structures)boundary-condition-specification SOP: identify the preconditions under which the theory applies (population, context, time range, etc.)falsifiability-check SOP (via the falsifiability-audit tactic): generate a falsification scenario for each hypothesisoperationalization SOP: provide draft measurement methods for the key variablesAfter each round, record:
Optional, no fixed order; the final leaf is always a sop.
| Tactic | When to use |
|---|---|
| falsifiability-audit | Tactic: hypothesis quality assurance — check falsifiability, repair failing hypotheses, complete operationalization and boundary-condition specification |
| theory-mechanism-extraction | Tactic: Core of the deductive path — start from theory to extract mechanisms, variables, and relationships, generating hypothesis candidates |