moai-foundation-philosopher

Apply a five-phase thinking framework to analyze strategic decisions and trade-offs.

1.2k|214|Updated Sep 16, 2025
One-click install
npx skills add https://github.com/modu-ai/moai-adk --skill moai-foundation-philosopher
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: moai-foundation-philosopher
Source: https://github.com/modu-ai/moai-adk/tree/main/.claude/skills/moai-foundation-philosopher
Command: npx skills add https://github.com/modu-ai/moai-adk --skill moai-foundation-philosopher

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill offers a strategic thinking framework that combines First Principles Analysis, Stanford Design Thinking, and MIT Systems Engineering to improve deep problem solving and decision making.

Core Features & Use Cases

  • First Principles Analysis: Break problems down to fundamental truths.
  • Design Thinking Integration: Divergent-convergent solution generation.
  • Systems Engineering: Systematic risk assessment and validation.
  • Five-Phase Thinking Process: Assumption audit, root-cause decomposition, alternative generation, trade-off analysis, and bias checks.
  • Cognitive Bias Awareness: Tools to detect and mitigate common thinking errors.

When to Use:

  • Architecture decisions affecting multiple files
  • Technology selection and performance vs maintainability trade-offs
  • Refactoring scope decisions
  • High-risk, high-impact planning

Quick Start

Initiate the Philosopher framework for a strategic decision and run through the five phases to surface assumptions and alternatives.

Frequently Asked Questions about moai-foundation-philosopher

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

FAQPage Schema
How do I structure decision-making for architecture and technology choices?

Strategic decision-making applies a structured five-phase framework—assumption audit, root-cause decomposition, alternative generation, trade-off analysis, and cognitive-bias checks—to evaluate architecture decisions, technology selection, and performance versus maintainability trade-offs systematically.

What is first-principles analysis and when should I use it for system design?

First-principles analysis breaks problems down to fundamental truths by decomposing assumptions into their core components. Use it for high-impact decisions like refactoring scope, long-term risk assessment, and technology selection where hidden assumptions drive poor outcomes.

How do I reduce cognitive bias when making engineering trade-offs?

Cognitive-bias awareness tools detect and mitigate common thinking errors during strategic planning. The framework surfaces hidden assumptions and generates alternatives through design-thinking divergence-convergence, revealing biases that narrow your decision options.

Can I apply systems engineering to validate architectural decisions?

Yes. Systems engineering provides systematic risk assessment and validation across your architecture decisions. It ensures trade-offs account for interconnected dependencies, long-term maintainability, and systemic risk—not just immediate performance gains.

What's the difference between this approach and informal decision-making?

Structured thinking combines First Principles Analysis, Design Thinking, and Systems Engineering into a validated multi-method framework. Informal approaches miss assumption audits, alternative generation, and bias checks—leading to incomplete trade-off analysis and brittle long-term decisions.