first-principles

Decompose decision premises into verified axioms through a structured 5-step workflow.

Updated May 6, 2026
One-click install
npx skills add https://github.com/HMWKR/claude-code-skills --skill first-principles-hmwkr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: first-principles
Source: https://github.com/HMWKR/claude-code-skills/tree/main/skills/first-principles
Command: npx skills add https://github.com/HMWKR/claude-code-skills --skill first-principles-hmwkr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of making suboptimal decisions based on unexamined, outdated, or incorrect assumptions and analogy-based reasoning, which often leads to wasted effort, failed projects, or missed opportunities in complex problem-solving scenarios.

Core Features & Use Cases

  • Systematic Assumption Decomposition: Breaks down implicit and explicit assumptions behind decisions using a structured Why Chain process to reach unassailable fundamental truths (axioms).
  • Premise Validation: Verifies the current validity of each axiom against real-world context, code, documentation, or domain knowledge to identify invalid or outdated premises.
  • Solution Reconstruction: Builds new, optimal solutions based only on verified fundamental truths, with a clear comparison to existing analogy-based approaches to highlight improvements.
  • Use Case: For example, when evaluating whether to migrate a legacy system to a new framework, use this Skill to challenge unexamined assumptions about the legacy system's constraints and rebuild a migration plan based on verified actual requirements.

Quick Start

Use the first-principles skill to challenge the assumptions behind our current team's decision to use a monolithic architecture for the new e-commerce platform and propose a rebuilt approach based on verified fundamental truths.

Frequently Asked Questions about first-principles

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I challenge assumptions during technical architecture evaluations?

To challenge assumptions during technical architecture evaluations, decompose decision premises using a structured Why Chain to reach fundamental truths, verify those axioms against real-world context, and reconstruct optimal solutions from the validated fundamentals.

What is first-principles problem solving and when should I use it?

First-principles problem solving is a method that eliminates suboptimal decision-making caused by analogy-based reasoning by breaking down premises to verifiable truths. Use it for strategy formulation, process optimization, and root cause analysis when underlying decision premises require validation.

How do I perform root cause analysis by breaking down unexamined premises?

Perform root cause analysis by systematically decomposing implicit and explicit assumptions behind decisions using a structured Why Chain process to reach unassailable fundamental truths, then validating each axiom against real-world context, code, or documentation to identify invalid premises.

What's the best way to validate outdated architecture constraints before a legacy system migration?

The best way to validate outdated architecture constraints before a legacy system migration is to challenge unexamined assumptions about the legacy system's constraints and rebuild a migration plan based only on verified fundamental truths rather than analogy-based reasoning.

Can I use this structured assumption decomposition workflow for process optimization?

Yes, you can use this structured assumption decomposition workflow for process optimization. It applies a 5-step workflow with user confirmation checkpoints for assumption decomposition, axiom verification, and solution reconstruction from verified fundamentals.

Why does analogy-based reasoning lead to suboptimal decision-making in software engineering?

Analogy-based reasoning leads to suboptimal decision-making in software engineering because it relies on unexamined, outdated, or incorrect assumptions, which often results in wasted effort, failed projects, or missed opportunities in complex problem-solving scenarios.