moai-foundation-philosopher

Analyze technical decisions by auditing assumptions, trade-offs, and cognitive biases.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/Jongsix/remote-claudecode --skill moai-foundation-philosopher-jongsix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: moai-foundation-philosopher
Source: https://github.com/Jongsix/remote-claudecode/tree/main/.claude/skills/moai-foundation-philosopher
Command: npx skills add https://github.com/Jongsix/remote-claudecode --skill moai-foundation-philosopher-jongsix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you slow down and structure complex technical decisions so you can avoid rushed choices, hidden assumptions, and preventable rework.

Core Features & Use Cases

  • Assumption Audit: Surfaces what you are taking for granted before committing to a path.
  • First Principles Analysis: Breaks problems down to root causes and fundamental constraints.
  • Trade-off Evaluation: Compares options across performance, maintainability, risk, and cost.
  • Bias Detection: Checks for anchoring, confirmation bias, sunk cost fallacy, and overconfidence.
  • Use Case: Choose between frameworks, assess refactor scope, or document an architecture decision with clear rationale.

Quick Start

Ask for a first-principles analysis of your decision, including assumptions, alternatives, trade-offs, and bias checks.

Frequently Asked Questions about moai-foundation-philosopher

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

FAQPage Schema
How do I evaluate architecture decisions using first principles analysis?

First principles analysis breaks technical decisions down to fundamental constraints and root causes, exposing hidden assumptions before you commit to an architecture path. This structured evaluation compares alternatives explicitly across performance, maintainability, risk, and cost.

What is the best way to compare technology selection trade-offs for a software project?

Comparing technology selection trade-offs requires evaluating options across performance, maintainability, risk, and cost dimensions. A structured trade-off evaluation surfaces hidden assumptions and checks for cognitive biases like anchoring or sunk cost fallacy before a recommendation.

How do cognitive biases like anchoring and sunk cost fallacy affect technical strategy?

Cognitive biases like anchoring, confirmation bias, and sunk cost fallacy distort technical strategy by inflating irrelevant data or past investments. Bias detection checks identify these distortions, ensuring architecture choices rely on explicit trade-off comparison rather than overconfidence.

Can I use root cause analysis to assess refactoring scope and decision risks?

Root cause analysis assesses refactoring scope by breaking complex problems down to fundamental constraints and exposing hidden assumptions. This process reveals decision risks and evaluates alternatives explicitly, preventing rushed choices and avoidable rework.

When do I need assumption audits for high-impact engineering decisions?

Assumption audits are needed for high-impact engineering decisions like framework selection or refactoring scope. They surface what you take for granted before committing to a path, ensuring structured evaluation of alternatives and explicit trade-off comparison.

What are the limitations of structured decision evaluation for technical trade-offs?

Structured evaluation of technical trade-offs slows down decision-making to prevent rushed choices and hidden assumptions. While it exposes root causes and decision risks, it requires comprehensive input and explicit alternative comparison, making it unsuitable for trivial implementation choices.