do-first-principles

Deconstructs problems to fundamental truths, classifies constraints, and reconstructs solutions from first principles.

2|Updated May 25, 2026
One-click install
npx skills add https://github.com/edheltzel/Do-Skills --skill do-first-principles-edheltzel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: do-first-principles
Source: https://github.com/edheltzel/Do-Skills/tree/main/skills/core/do-first-principles
Command: npx skills add https://github.com/edheltzel/Do-Skills --skill do-first-principles-edheltzel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often reason by analogy, copying existing solutions and treating conventions, market prices, and inherited policies as immutable constraints. This Skill breaks that pattern by deconstructing a problem to its irreducible fundamental truths, separating hard constraints from soft constraints and unvalidated assumptions, then rebuilding an optimal solution from fundamentals alone. ## Core Features & Use Cases - Deconstruct Workflow: Breaks any problem, system, or cost structure into constituent parts and real values, exposing the gap between stated prices and fundamental costs. - Challenge Workflow: Classifies every stated constraint as hard (physics), soft (policy/choice), or assumption (unvalidated belief), surfacing hidden constraints worth challenging. - Reconstruct Workflow: Generates blank-slate solution options built only from hard constraints, with cross-domain insights and an explicit comparison against the current approach. - Use Case: Facing a $10,000/month cloud bill accepted as "just what it costs," run the analysis to discover the actual compute need is $2,000 and the remaining $8,000 is a chosen convenience, then reconstruct a right-sized architecture. ## Quick Start Use the first principles skill to analyze why our cloud hosting costs $10,000 per month and reconstruct a cheaper architecture from the fundamental requirements.

Frequently Asked Questions about do-first-principles

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

FAQPage Schema
How do I apply first principles thinking to a technical problem?▼

Run the three workflows in sequence: Deconstruct breaks the problem into constituent parts and real values, Challenge classifies each constraint as hard, soft, or assumption, and Reconstruct builds a new solution using only the hard constraints. The output includes a parts breakdown, constraint table, and reconstructed solution.

What is the difference between reasoning by analogy and first principles?▼

Reasoning by analogy copies existing solutions with slight variations, inheriting everyone else's assumptions. First principles reasoning asks what the problem is actually made of, separates physics from convention, and rebuilds from only the irreducible facts.

How do I tell if a constraint is a hard constraint or just a convention?▼

Ask whether violating it would break a law of physics or mathematics. If a decision-maker could change it, like "we use REST APIs" or a budget limit, it is a soft constraint. If it is an untested belief like "users won't accept that," it is an assumption to validate.

When should I not use first principles analysis?▼

This skill is for analysis and reasoning, not implementation or structural feedback-loop problems. If the task is to directly fix or build something, do the work directly rather than running a deconstruction. It is also high-effort, so trivial decisions do not warrant it.

Can other skills or workflows invoke first principles analysis?▼

Yes. The skill documents an integration pattern where architects, red-team reviewers, and pentesters invoke the Deconstruct or Challenge workflows on stated constraints, security models, or requirements before proceeding with their own analysis.