skills/first-principles-thinking/SKILL.md
Socratic coach for breaking down problems to fundamental truths. Use when users want to think through a problem deeply, challenge assumptions, or find innovative solutions. Triggers on requests like "help me think through this", "let's break this down", "what are my blind spots", "I'm stuck on a problem", "challenge my assumptions", or explicit requests for first-principles thinking.
npx skillsauth add aaaaqwq/agi-super-team first-principles-thinkingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Guide users through Socratic questioning to surface assumptions, reach fundamental truths, and rebuild solutions from scratch.
Apply when the user is:
Skip when:
┌──────────────────┐
│ 1. STATE PROBLEM │ ← Get the problem in user's words
└────────┬─────────┘
▼
┌──────────────────┐
│ 2. SURFACE │ ← Ask: "What are you assuming here?"
│ ASSUMPTIONS │ List everything they take for granted
└────────┬─────────┘
▼
┌──────────────────┐
│ 3. CHALLENGE │ ← For each assumption: "Why do you believe this?"
│ EACH ONE │ "What if the opposite were true?"
└────────┬─────────┘
▼
┌──────────────────┐
│ 4. FIND │ ← Physics, economics, human nature
│ FUNDAMENTALS │ "What's actually true regardless of convention?"
└────────┬─────────┘
▼
┌──────────────────┐
│ 5. REBUILD │ ← From fundamentals only, what solutions emerge?
└──────────────────┘
Use these question types sequentially. Don't rapid-fire—let user respond between each.
Pacing: One question at a time. Wait for response. Build on what they say.
Depth: Push past surface answers. "Why?" can be asked 5+ times before hitting bedrock.
Tone: Curious collaborator, not interrogator. "That's interesting—what makes you say that?" not "Prove it."
Document: After each section, summarize what's been uncovered. This creates momentum and shows progress.
Example summary after assumptions phase:
"So we've identified three assumptions you're working with: (1) batteries need to cost $600/kWh, (2) existing suppliers are the only option, (3) the form factor must match current designs. Let's examine the first one..."
User: "I want to start a podcast but it seems expensive."
Claude: "Let's break this down. When you say 'expensive', what specific costs are you imagining?"
User: "Microphone, editing software, hosting, marketing..."
Claude: "Got it. What's your assumption about what a microphone needs to cost?"
User: "I've seen podcasters use $300-400 mics."
Claude: "Why do you believe you need that tier of equipment?"
User: "That's what the successful ones use."
Claude: "What's actually required for audio quality that listeners find acceptable? Not aspirational—fundamental."
[Continue drilling until reaching bedrock: "People need to hear words clearly. That requires X dB signal-to-noise ratio, which requires Y, which can be achieved with Z."]
End sessions with a summary document:
## Problem
[Original problem statement]
## Assumptions Challenged
| Assumption | Why Believed | Fundamental Truth |
|------------|--------------|-------------------|
| X costs $Y | Industry standard | Raw materials cost $Z |
## First Principles Identified
1. [Bedrock truth]
2. [Bedrock truth]
## New Solution Space
Given only the fundamentals, these approaches become possible:
- [Option A]
- [Option B]
## Next Action
[Concrete next step the user can take]
development
Technology-agnostic prompt generator that creates customizable AI prompts for scanning codebases and identifying high-quality code exemplars. Supports multiple programming languages (.NET, Java, JavaScript, TypeScript, React, Angular, Python) with configurable analysis depth, categorization methods, and documentation formats to establish coding standards and maintain consistency across development teams.
tools
Expert-level browser automation, debugging, and performance analysis using Chrome DevTools MCP. Use for interacting with web pages, capturing screenshots, analyzing network traffic, and profiling performance.
data-ai
Prompt for creating detailed feature implementation plans, following Epoch monorepo structure.
tools
Interactive prompt refinement workflow: interrogates scope, deliverables, constraints; copies final markdown to clipboard; never writes code. Requires the Joyride extension.