First Principles Decomposer

Break any problem down to fundamental truths, then rebuild solutions from atoms up. Use when user says "firstp", "first principles", "from scratch", "what are we assuming", "break this down", "atomic", "fundamental truth", "physics thinking", "Elon method", "bedrock", "ground up", "core problem", "strip away", or challenges assumptions about how things are done.

Security Scan

This is an instruction-only, methodology skill for breaking problems into fundamentals; its requirements and runtime instructions are consistent with that purpose and it does not request credentials, install software, or perform file/network operations.

Purpose & Capability

Name/description (first-principles decomposition) match the SKILL.md content and included references. The skill requires no binaries, no env vars, no config paths — all coherent for a purely advisory framework skill.

Instruction Scope

Runtime instructions are limited to asking clarifying questions, listing assumptions, deriving fundamentals, and proposing rebuilt solutions. The SKILL.md does not instruct reading local files, environment variables, or sending data to external endpoints.

Install Mechanism

No install spec and no code files that execute — the skill is instruction-only, which is the lowest-risk install model.

Credentials

The skill declares no environment variables, credentials, or config path access. There are no disproportionate secret or credential requests relative to the documented purpose.

Persistence & Privilege

Flags show always:false and normal model invocation settings. The skill does not request persistent or elevated presence or modification of other skills/configuration.

Assessment

This skill appears internally coherent and low-risk because it only contains written methodology and asks clarifying questions. Before installing, consider: (1) provenance — the source/homepage is unknown, so you can't audit the author or track updates, (2) do not paste secrets or sensitive files into prompts (the skill is advisory but user input can contain secrets), and (3) if you allow the agent to chain this skill with others (the SKILL.md mentions integrations), review those other skills' permissions and trustworthiness because combined workflows can expand what the agent does. If you need stronger assurance, request a visible source repository or homepage from the publisher before installing.

When To Use

• Designing new products or features
• Feeling stuck on a complex problem
• Existing solutions seem overcomplicated
• Need to challenge assumptions
• Starting any new project or initiative

The Process

Phase 1: Identify Assumptions

Ask: "What am I assuming to be true that might not be?" List every assumption embedded in the current approach.

Phase 2: Break to Atoms

For each assumption, ask: "What is the most fundamental truth here?" Keep asking "why?" until you hit bedrock facts.

Phase 3: Rebuild From Truth

Starting ONLY from verified fundamentals, ask: "What's the simplest solution that addresses the core need?"

Interactive Flow

When user invokes this skill:

1. Clarify the problem (1-2 questions max)
2. Surface assumptions - list what's being taken for granted
3. Decompose to fundamentals - show the atomic truths
4. Rebuild solution - construct from ground up
5. Compare - show how this differs from conventional approach

Output Format

PROBLEM: [stated problem]

ASSUMPTIONS IDENTIFIED:
1. [assumption] → Challenge: [why this might be wrong]
2. [assumption] → Challenge: [why this might be wrong]

FUNDAMENTAL TRUTHS:
• [bedrock fact 1]
• [bedrock fact 2]
• [bedrock fact 3]

REBUILT SOLUTION:
[New approach built only from fundamentals]

VS CONVENTIONAL:
[How this differs from the obvious approach]

Example Triggers

• "Break down our parent communication problem from first principles"
• "I want to rethink how we do [X] from the ground up"
• "What are we assuming about [problem] that might be wrong?"

Integration

This skill compounds with:

• inversion-strategist - After rebuilding from fundamentals, invert to find what would guarantee failure of the new approach
• second-order-consequences - Project downstream effects of implementing the rebuilt solution
• pre-mortem-analyst - Stress-test the rebuilt solution by imagining its failure
• six-thinking-hats - Apply all six perspectives to validate each fundamental truth identified

Skill Metadata

Created: 2026-01-06 Last Updated: 2026-01-06 Author: Artem Version: 1.0

---

See references/framework.md for detailed methodology See references/examples.md for Artem-specific examples See references/integrated-frameworks.md for Stanford Design Thinking + MIT Systems Engineering combo