moai-foundation-philosopher

Apply the Philosopher Framework to produce structured decision analyses.

1|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/GoosLab/moai-rank --skill moai-foundation-philosopher-gooslab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: moai-foundation-philosopher
Source: https://github.com/GoosLab/moai-rank/tree/main/.claude/skills/moai-foundation-philosopher
Command: npx skills add https://github.com/GoosLab/moai-rank --skill moai-foundation-philosopher-gooslab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Philosopher Framework solves complex decision problems through structured, principled analysis.

Core Features & Use Cases

  • Combines First Principles Analysis, Stanford Design Thinking, and MIT Systems Engineering for rigorous decision-making.
  • Guides assumption auditing, alternative generation, trade-off analysis, and cognitive bias checks across projects.
  • Use cases include architecture decisions, technology selection, and large-scale trade-off analysis.

Quick Start

Apply the Philosopher Framework to a design problem and produce a structured decision analysis.

Frequently Asked Questions about moai-foundation-philosopher

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

FAQPage Schema
How do I apply first principles analysis to complex architecture decisions?

Structured decision analysis applies a five-phase workflow combining first principles analysis, design thinking, and systems engineering to audit assumptions, generate alternatives, and mitigate cognitive bias for complex architecture decisions.

What is the best way to mitigate cognitive bias during technical trade-off analysis?

Cognitive bias mitigation occurs through structured assumption auditing and alternative generation within a five-phase workflow, ensuring technical trade-off analysis evaluates root causes rigorously rather than relying on heuristic shortcuts.

Can I use this framework for product strategy and technology selection?

The framework supports product strategy and technology selection by applying systems engineering and design thinking to evaluate large-scale trade-offs and generate structured decision records for complex problems.

How do I conduct a root-cause analysis for design problems using systems engineering?

Root-cause analysis is achieved through the framework's five-phase workflow, which integrates systems engineering and assumption auditing to isolate fundamental drivers of design problems before generating alternatives.

When should I use a structured decision record instead of standard design thinking?

Use a structured decision record for large-scale trade-off analysis and architecture decisions where bias mitigation and rigorous assumption auditing are required, whereas standard design thinking focuses more on user-centric ideation.