first-principles-thinking
/first-principles-thinking
Discover business opportunities and judge income paths by exposing hidden assumptions, reframing the transaction, and designing a discriminating next test. Also use for consequential product, work or life decisions with uncertain premises, or explicit first-principles/第一性原理 requests. Not for routine execution or simple factual lookup.
- Author
- CharlexH ↗
- Repository
- first-principles-council ↗
- Licence
- MIT
- Last repository change
- 04.11.2026
Assessment and security
- Files in this package
- 3
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 04.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Discover business opportunities and judge income paths by exposing hidden assumptions, reframing the transaction, and designing a discriminating next test. Also use for consequential product, work or life decisions with uncertain premises, or explicit first-principles/第一性原理 requests. Not for routine execution or simple factual lookup.
Original author description
Discover business opportunities and judge income paths by exposing hidden assumptions, reframing the transaction, and designing a discriminating next test. Also use for consequential product, work or life decisions with uncertain premises, or explicit first-principles/第一性原理 requests. Not for routine execution or simple factual lookup.
How it works
- Start with the decision
- Apply the useful lenses, not a checklist
- Deliver a usable judgment
SKILL.md preview
--- name: first-principles-thinking description: Discover business opportunities and judge income paths by exposing hidden assumptions, reframing the transaction, and designing a discriminating next test. Also use for consequential product, work or life decisions with uncertain premises, or explicit first-principles/第一性原理 requests. Not for routine execution or simple factual lookup. metadata: version: "1.3.0" --- # First Principles Council Help the user choose what to do next, and what evidence would change that choice. Answer in their language. Use one integrated analysis, not speeches by famous people or mandatory subagents. The five method lenses below are inspirations, not impersonations, endorsements, or a proof of effectiveness. Sources and limits: [method notes](references/method-notes.md), read only when attribution or definitions matter. ## Start with the decision Separate the desired outcome from the proposed means: a product, channel, idle asset, price, or business model may be a hypothesis. Preserve the user's priorities, constraints, existing commitments, and authorized execution. Do not reopen a settled decision without a material reason. For life decisions, do not replace personal values with income maximization. Identify the premise most likely to change the next investment of time or money. Distinguish supplied observations, verified external facts, constraints, interpretations, and unknowns. Business “fundamentals” are often provisional causal claims, not physical laws. Stop decomposing when the distinction changes an action. ## Apply the useful lenses, not a checklist **Mechanism — inspired by Feynman's scientific integrity.** Explain how an action could produce the desired result. If the proposed solution were free and perfect, what could still prevent that result? What observation would undermine the favored explanation? A plausible story is not causal evidence; alternatives and counterexamples matter. **Switching — inspired by Christensen's jobs-to-be-done.** Reconstruct a specific occasion: who needs progress, what triggers action, how they cope now, and why they would switch now. Separate user, organizer, payer, approver, and channel. Follow evidence within the same person or transaction; never combine A's pain, B's budget and C's access into an imaginary customer. Existing workarounds, delay and doing nothing are competitors. Buying once, using successfully and buying again are different evidence. **Boundaries — inspired by Kim and Mauborgne.** When the framing limits the options, consider changing one consequential boundary: buyer, purchase occasion, scope, adjacent step, or delivery resource. What useful outcome remains if the idle asset or proposed product disappears? What could be removed while preserving the outcome? Generate only a few materially different routes anchored in actual clues and accessible resources. Label an unsupported new route as a hypothesis. Compare against the existing paid route and doing nothing; a narrower offer or the original business may be best. Do not force novelty, a pivot, manual service, or a “10×” claim. **Behavior — inspired by Fitzpatrick.** Separate past behavior, stated interest, promised commitment and fulfilled commitment. Compliments, free usage, referrals and organizer enthusiasm are leads, not revenue. A payment supports that transaction, not automatically a new segment, product or durable market. Ask about the last concrete event and the current alternative before asking whether someone likes an idea. Missing evidence is not evidence of absence. **Decision experiment — inspired by Torres.** Test the uncertainty that could change the preferred route, not whatever is easiest to measure. Name the favored explanation and a credible rival that imply different actions. Choose the smallest feasible observation or offer that distinguishes them. Explain briefly: - Who must be reached, what must actually happen, and what is held comparable. - Which result supports continuing, changing the offer, or stopping. - When a negative result is inconclusive: the payer was never reached, timing was wrong, delivery failed, or the test did not manipulate the suspected barrier. Separate a learning stop from a business stop: a test may be too costly to continue without proving no market exists. Do not prescribe universal interview counts, score cutoffs, or two-order “validation.” If a numerical threshold is useful, tie it to this user's constraints or economics and label it provisional. Do not demand scientific certainty before a reversible small action. Payment is useful for willingness to pay; it does not diagnose every reason for nonpurchase. ## Deliver a usable judgment Lead with a conditional recommendation and the reason it beats the strongest alternative. Make the changed framing visible if it matters. Give the decisive assumption, one prioritized next test, and the observation that changes your recommendation. Fit depth to stakes; do not print five lens sections unless useful. Ask only for missing information that blocks the next decision, otherwise state an assumption and proceed. For earning decisions, account for access to buyers, all relevant work and delivery costs, opportunity cost, timing and repeatability. Computation can check feasibility; it cannot create demand. Preserve proven income while testing speculative routes unless the user's objective requires otherwise. A test budget is a ceiling, not a spending target. When fresh facts arrive, update the affected claim and action explicitly; don't rewrite all prior evidence as invalid. Check current or professional facts with the host's tools and policies; disclose unavailable verification. Never invent research, interviews, purchases, probabilities or completed experiments. Advice alone does not authorize contacting customers, spending, or publishing. No earnings guarantees.
Files in this package (3)
- SKILL.md 6 KB
- agents/openai.yaml 1 KB
- references/method-notes.md 2 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · CharlexH/first-principles-council | 90 | MIT |
| diaryofamademan/skills | 100 | MIT |
| phronia/phronia | 100 | AGPL-3.0 |
| ysskrishna/ai-agent-skills | 100 | MIT |
| fzfclee/consulting-skills | 100 | Apache-2.0 |
| mindfold-ai/trellis | 100 | AGPL-3.0 |
| jacob-balslev/skill-graph | 100 | Apache-2.0 |
| Amey-Thakur/AI-SKILLS | 90 | MIT |
Database snapshot: 13.11.2026 · package version efb823630bd0 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100first-principles
Question assumptions and reason from fundamentals instead of analogy or convention. Use when asked to 'analyze from first principles', 'think from scratch', 'question this design', 'is this the right approach', 'is there a better solution', 'challenge assumptions', 'should this… - 90principles-first
First-principles and design thinking on product, architecture and communication decisions. Use when framing a problem, weighing a tradeoff, adding scope, or hearing "should we…" and "that's how it's always done". Explicit: "think first principles", "step back". - 90data-product-thinking
First-principles reasoning for data product decisions. Frames problems as data products, not dashboards or pipelines. Use when evaluating data product strategy, making build-vs-buy decisions, scoping data product features, assessing product-market fit for data offerings, or when… - 100product-discovery
Discover product requirements from human stakeholders — map who to talk to, ask questions that surface hidden assumptions, detect gaps in real time, resolve conflicts, and translate conversations into structured SDD specs. Phase 0 upstream of Spec-Driven Development. Also grill… - 100meta-first-principles
Apply first principles thinking to break problems down to fundamental truths and reason up from there. Use this skill when the user is stuck in conventional thinking, needs to challenge assumptions, find breakthrough solutions, or evaluate whether something is truly impossible… - 90design-interrogation
Relentlessly interview the user about a plan, design, or feature spec to surface unresolved decisions, hidden assumptions, and edge cases. Use when the user says "grill me", "stress-test this plan", "poke holes in my design", "what am I missing", or before committing to a plan…