Skill

Audit Assumptions with First Principles

First-principles auditor that mines, classifies, and risk-ranks hidden assumptions behind a decision, then rebuilds the conclusion.


90
Spark score
out of 100
Updated last month
Version 13.1.1

Add to Favorites

Why it matters

Deconstruct complex decisions and beliefs by rigorously auditing assumptions from first principles, ensuring conclusions are built on verifiable truths.

Outcomes

What it gets done

01

Reframe the core problem to ensure it's correctly defined.

02

Systematically mine and classify hidden assumptions across multiple layers.

03

Rank assumptions by fragility and impact to prioritize investigation.

04

Reconstruct conclusions based solely on verified premises.

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/ag-axiom | bash

Overview

Axiom - First-Principles Assumption Auditor / 第一性原理拆解器

First-principles assumption auditor that strips a decision or belief down to its hidden assumptions across three depth layers, classifies each into one of four types (physical fact, historical convention, subjective belief, interest-driven), risk-ranks them by fragility times impact, and rebuilds the conclusion from only the assumptions that survive scrutiny. Responds fully in whichever language the user writes in. Use it before a major life or career decision, to stress-test a business hypothesis, or whenever you suspect a belief might be wrong but can't articulate why. Not a quick framework fill-in-the-blank - it's meant for genuine assumption prosecution on decisions that matter.

What it does

Axiom is a first-principles assumption auditor: it strips a question down to its irreducible truths, then rebuilds the conclusion from there, rather than filling in a generic decision framework. It runs a five-phase process - reframe the real problem, mine 8-12 hidden assumptions across surface/middle/deep layers, classify each assumption into one of four types, risk-rank them by fragility times impact, and reconstruct the conclusion using only the assumptions that survive scrutiny. It auto-detects and responds entirely in whichever language the user writes in (English or Chinese, without mixing).

When to use - and when NOT to

Use it when a major life or career decision is on the table (quitting a job, starting a company, buying a house), when stress-testing a business direction or product hypothesis, when a belief feels possibly wrong but hard to articulate why, or whenever someone explicitly asks to "think from first principles" or "break it down." It's designed for genuine assumption prosecution, not quick framework fill-in-the-blank - Phase 1 deliberately refuses to start decomposing assumptions until the real question is confirmed, since many people ask "should I quit my job?" when the actual question is "why can't I grow in my current role?"

Inputs and outputs

Phase 1 reframes the core question and asks the user to confirm it before proceeding. Phase 2 mines assumptions across three layers - surface (obviously stated, e.g. "I need more money"), middle (industry convention or common wisdom, e.g. "a degree is required for good jobs"), and deep (never questioned, feels like gravity, e.g. "success means financial independence") - targeting 8-12 concrete assumptions and rejecting vague ones. Phase 3 labels each assumption as a Physical Fact (accept it, don't waste energy questioning it), Historical Convention (check if the environment has changed since it became true), Subjective Belief (trace who told you this and seek counter-evidence), or Interest-Driven (trace who profits from the narrative) - each type implying a different challenge strategy, and the classification itself is often the insight. Phase 4 scores each assumption on Fragility (1-5, how easily disproven) times Impact (1-5, how much the conclusion collapses if wrong), outputting the Top 3 highest-risk assumptions with a specific, actionable verification question for each. Phase 5 rebuilds the conclusion from only the surviving assumptions, explicitly comparing "original thinking" versus "rebuilt thinking" side by side - if the rebuilt conclusion matches the original, it must explain why rather than silently passing; if there's no time for a full reconstruction, it outputs the single most important thing to verify first.

Integrations

Deeper scenario checklists and assumption-type identification guidance live in references/scenarios.md and references/assumption-types.md, which the skill consults when detecting the user's specific scenario type or classifying an ambiguous assumption.

Who it's for

Anyone facing a high-stakes decision or a belief they suspect might be wrong, who wants a rigorous, language-matched process for surfacing and testing hidden assumptions rather than a generic pros-and-cons list.

FAQ

Common questions

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.