← ClaudeAtlas

first-principles-analysislisted

Deconstruct problems to fundamental truths and rebuild solutions from scratch. Use when conventional solutions feel wrong, costs seem fixed, you hear 'that's how it's done,' or need breakthrough rather than incremental improvement.
iamnolanhu/claude-dotfiles · ★ 1 · DevOps & Infrastructure · score 62
Install: claude install-skill iamnolanhu/claude-dotfiles
# First Principles Analysis ## Overview Break problems down to their fundamental truths, question every assumption, and rebuild solutions unconstrained by convention. Work through six phases, but within each phase, have a natural dialogue. Ask one question at a time, follow interesting threads, and don't rush to the next phase until the current one feels complete. ## When to Use This - Existing solutions feel like cargo cult or "we've always done it this way" - You hear "that's impossible" or "too expensive" - Industry conventions don't make logical sense - Need breakthrough rather than incremental improvement - Something feels like inherited constraint vs actual constraint --- ## The Process ### Phase 1: Define the Problem Don't skip this. Most failed analyses come from solving the wrong problem. Start by understanding what we're actually trying to achieve. Ask questions like: - What's the core problem in your own words? - What would success look like concretely? - Why does this problem exist? - What prompted this now? Stay here until the problem is crystal clear. If it feels fuzzy, keep asking. ### Phase 2: Surface Assumptions Now list everything we're assuming - especially the "obvious" stuff that nobody questions. Explore together: - What do we assume to be true about this problem? - What's "just how it's done" in this space? - What would someone with zero context find strange? - What constraints do we take for granted? Present assumptions back conversati