research-first-principle-deconstructor

Rigorous Socratic interrogator and research architect that helps researchers overcome incremental thinking by applying First Principles analysis. Use when a researcher presents a research problem, proposed methodology, draft idea, or scientific hypothesis and wants to expose hidden assumptions, identify fundamental physical/mathematical constraints, generate unconventional radical alternatives, or deepen mechanistic understanding through probing questions. Triggers on phrases like "I want to improve X by doing Y", academic research brainstorming, scientific hypothesis generation, or any request to stress-test, challenge, or deconstruct a research idea. Do NOT trigger for pure literature reviews, writing assistance, or non-research tasks.

16 stars

Best use case

research-first-principle-deconstructor is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Rigorous Socratic interrogator and research architect that helps researchers overcome incremental thinking by applying First Principles analysis. Use when a researcher presents a research problem, proposed methodology, draft idea, or scientific hypothesis and wants to expose hidden assumptions, identify fundamental physical/mathematical constraints, generate unconventional radical alternatives, or deepen mechanistic understanding through probing questions. Triggers on phrases like "I want to improve X by doing Y", academic research brainstorming, scientific hypothesis generation, or any request to stress-test, challenge, or deconstruct a research idea. Do NOT trigger for pure literature reviews, writing assistance, or non-research tasks.

Teams using research-first-principle-deconstructor should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/research-first-principle-deconstructor/SKILL.md --create-dirs "https://raw.githubusercontent.com/diegosouzapw/awesome-omni-skill/main/skills/development/research-first-principle-deconstructor/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/research-first-principle-deconstructor/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How research-first-principle-deconstructor Compares

Feature / Agentresearch-first-principle-deconstructorStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Rigorous Socratic interrogator and research architect that helps researchers overcome incremental thinking by applying First Principles analysis. Use when a researcher presents a research problem, proposed methodology, draft idea, or scientific hypothesis and wants to expose hidden assumptions, identify fundamental physical/mathematical constraints, generate unconventional radical alternatives, or deepen mechanistic understanding through probing questions. Triggers on phrases like "I want to improve X by doing Y", academic research brainstorming, scientific hypothesis generation, or any request to stress-test, challenge, or deconstruct a research idea. Do NOT trigger for pure literature reviews, writing assistance, or non-research tasks.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

SKILL.md Source

# Research First Principle Deconstructor

## Overview

Transform research ideas from incremental improvements into genuinely novel contributions by systematically dismantling assumptions and rebuilding from fundamental truths. Apply all 4 steps in sequence for every research input.

## The 4-Step Algorithm

### Step 1 — Assumption Extraction (The Teardown)

Identify and explicitly list all implicit assumptions, inherited conventions, and "common practices" embedded in the user's idea. Target 5–8 distinct assumptions. Label each clearly:

- "You are assuming that..."
- "This approach inherits the convention that..."
- "The standard practice here presupposes..."

Scan across these categories:
- **Substrate/material**: "must use X" (silicon, transformers, CRISPR, lithium)
- **Process/mechanism**: sequential processing, end-to-end training, iterative refinement
- **Optimization target**: the chosen metric may itself be the wrong thing to optimize
- **Scale heuristics**: more data = better, larger = smarter, finer resolution = more precise
- **Causal mechanism**: that the proposed intervention actually works via the claimed pathway

### Step 2 — Truth Reduction (The Core)

Strip all conventions. State only what is **physically, mathematically, or logically unavoidable** — things that cannot be circumvented regardless of engineering ingenuity.

Format each as:
> **Fundamental Truth**: [irreducible constraint — physical law, mathematical bound, or logical necessity]

Aim for 2–4 truths. Draw from thermodynamics, information theory, complexity theory, quantum mechanics, biochemistry, or formal logic as appropriate — including across domain boundaries. Step 3 may only build from these truths, not from the discarded assumptions.

### Step 3 — Orthogonal Recombination (The Novelty Generator)

Generate exactly **3 radical approaches** constructed solely from the fundamental truths in Step 2. Treat the original idea as fully discarded.

For each approach:
1. **Name it** (a short, evocative label)
2. **Describe the core mechanism** (2–3 sentences)
3. **State which conventional assumption it deliberately violates**

Litmus test: if any approach could be described as "doing more of what already exists" or as an incremental extension of the user's original idea, discard it and generate a more radical alternative. The goal is approaches that would genuinely surprise a domain expert.

### Step 4 — Depth Drilling (The 5-Whys)

Generate 3–5 sharply probing questions targeting the mechanistic **"Why"**, not the phenomenological **"What"**. Questions must force the researcher to descend from observation to root-cause mechanics.

Effective question frames:
- "Physically/mathematically, **why** does your proposed mechanism produce [claimed effect]?"
- "What is the **theoretical upper bound** of [proposed method] and what first principle establishes it?"
- "If [assumed condition] were false, would your mechanism still hold? Derive why."
- "At the [atomic/quantum/lattice/logical] level, what is the **exact interaction** that causes [X]?"

Reject any question answerable with a literature citation. Target questions requiring the researcher to derive or construct an answer from first principles.

## Output Format

```
## First Principles Deconstruction

### Step 1: Assumption Extraction
1. You are assuming that...
2. This approach inherits the convention that...
[5–8 total]

### Step 2: Fundamental Truths
- **Fundamental Truth**: [irreducible constraint]
- **Fundamental Truth**: [irreducible constraint]
[2–4 total]

### Step 3: Radical Recombinations
**Approach 1 — [Name]**
[Mechanism. Which assumption this violates.]

**Approach 2 — [Name]**
[Mechanism. Which assumption this violates.]

**Approach 3 — [Name]**
[Mechanism. Which assumption this violates.]

### Step 4: Depth Drilling Questions
1. [Root-cause mechanics question]
2. [Theoretical limit question]
3. [Hidden mechanism question]
[4–5 optional]
```

## Behavioral Guidelines

- **The teardown must be complete.** Do not soften or validate the user's approach in Steps 1–2. The point is to dismantle it entirely before rebuilding.
- **Step 3 must be genuinely orthogonal.** Novelty is the only criterion. Feasibility is secondary — a radical idea that requires new physics is more valuable at this stage than a safe incremental one.
- **Step 4 must be uncomfortable.** Good questions expose gaps the researcher has not thought about. If a researcher can answer a question immediately from memory, it is not deep enough.
- **Draw across domain boundaries.** A materials science problem may have its fundamental truth in quantum mechanics. A machine learning problem may be bounded by information theory. Cross-domain analogies are a primary source of genuine novelty.
- **Do not skip or reorder steps.** The sequence is load-bearing: Step 3 is only valid because it builds from Step 2; Step 4 interrogates the original idea's mechanism, not the Step 3 alternatives.

## Calibration Examples

Read `references/examples.md` when you need to calibrate the expected depth, rigor, and style. It contains two fully worked examples: one in AI/NLP and one in Materials Science/Energy.

Related Skills

staging-ui-first

16
from diegosouzapw/awesome-omni-skill

UI-first implementation and staging workflow for Zeus. Use when building routes, components, or forms before backend integration, or when creating UI scaffolds with mock data and later wiring to real APIs.

ring:pre-dev-research

16
from diegosouzapw/awesome-omni-skill

Gate 0 research phase for pre-dev workflow. Dispatches 4 parallel research agents to gather codebase patterns, external best practices, framework documentation, and UX/product research BEFORE creating PRD/TRD. Outputs research.md with file:line references and user research findings.

research-web

16
from diegosouzapw/awesome-omni-skill

Deep web research with parallel investigators, multi-wave exploration, and structured synthesis. Spawns multiple web-researcher agents to explore different facets of a topic simultaneously, launches additional waves when gaps are identified, then synthesizes findings. Use when asked to research, investigate, compare options, find best practices, or gather comprehensive information from the web.\n\nThoroughness: quick for factual lookups | medium for focused topics | thorough for comparisons/evaluations (waves continue while critical gaps remain) | very-thorough for comprehensive research (waves continue until satisficed). Auto-selects if not specified.

research

16
from diegosouzapw/awesome-omni-skill

Technical research methodology with YAGNI/KISS/DRY principles. Phases: scope definition, information gathering, analysis, synthesis, recommendation. Capabilities: technology evaluation, architecture analysis, best practices research, trade-off assessment, solution design. Actions: research, analyze, evaluate, compare, recommend technical solutions. Keywords: research, technology evaluation, best practices, architecture analysis, trade-offs, scalability, security, maintainability, YAGNI, KISS, DRY, technical analysis, solution design, competitive analysis, feasibility study. Use when: researching technologies, evaluating architectures, analyzing best practices, comparing solutions, assessing technical trade-offs, planning scalable/secure systems.

research-free

16
from diegosouzapw/awesome-omni-skill

APIキー不要の統合リサーチスキル。Claude Code組み込みのWebSearch/WebFetchを使用。他人に配布してもそのまま使える。

research-cog

16
from diegosouzapw/awesome-omni-skill

#1 on DeepResearch Bench (Feb 2026). Deep research agent powered by CellCog. Market research, competitive analysis, stock analysis, investment research, academic research with citations.

research-cascade

16
from diegosouzapw/awesome-omni-skill

Multi-source research orchestration. Chains deepwiki, submodules, WebSearch, and codebase search. Defines when to escalate and how to synthesize findings.

repo-research-analyst

16
from diegosouzapw/awesome-omni-skill

Conducts thorough research on repository structure, documentation, conventions, and implementation patterns. Use when onboarding to a new codebase or understanding project conventions.

principles

16
from diegosouzapw/awesome-omni-skill

Provides development principles, guidelines, and VibeCoder guidance. Use when user mentions 原則, principles, ガイドライン, guidelines, VibeCoder, 安全性, safety, 差分編集, diff-aware. Triggers: 原則, principles, ガイドライン, VibeCoder, 安全性, 差分編集. Do not use for actual implementation - use impl skill instead.

mobile-first-design-rules

16
from diegosouzapw/awesome-omni-skill

Focuses on rules and best practices for mobile-first design and responsive typography using tailwind.

lead-research-assistant

16
from diegosouzapw/awesome-omni-skill

Researches and identifies potential customers, leads, and business opportunities for your product or service. Analyzes your offering, finds relevant companies and decision makers, provides contact information, and suggests outreach strategies. Use when looking for leads, researching target customers, identifying decision makers, or planning sales outreach.

koan-entity-first

16
from diegosouzapw/awesome-omni-skill

Entity<T> patterns, GUID v7 auto-generation, static methods vs manual repositories