moai-foundation-philosopher

Guides strategic technical decisions through assumption audits, first principles decomposition, and trade-off analysis.

2|Updated May 27, 2026
One-click install
npx skills add https://github.com/yekinya/moai-novel --skill moai-foundation-philosopher-yekinya
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: moai-foundation-philosopher
Source: https://github.com/yekinya/moai-novel/tree/main/moai-novel/.claude/skills/moai-foundation-philosopher
Command: npx skills add https://github.com/yekinya/moai-novel --skill moai-foundation-philosopher-yekinya

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Complex architecture and technology decisions are often made on unexamined assumptions, first-idea anchoring, and hidden trade-offs, leading to rework and project failure. This Skill provides a structured five-phase thinking framework that surfaces assumptions, finds root causes, generates alternatives, compares trade-offs, and checks for cognitive biases before committing to a decision. ## Core Features & Use Cases - Five-Phase Decision Process: Assumption Audit, First Principles Decomposition (Five Whys), Alternative Generation, Weighted Trade-off Analysis, and Cognitive Bias Check. - Decision Documentation: Strategic Decision Record template with weighted scoring matrices, trade-off records, and review triggers for architecture decisions. - Deep-Dive Modules: Dedicated modules for assumption matrices, first principles, trade-off analysis, and cognitive bias mitigation, plus worked examples for technology selection, performance optimization, and refactoring scope. - Use Case: When choosing a state management library for a React app, run the framework to audit team-skill assumptions, generate four candidate options, score them against weighted criteria, and document the accepted trade-offs with a review trigger. ## Quick Start Ask the AI to apply the Philosopher framework to evaluate architecture options for your current technology selection decision.

Frequently Asked Questions about moai-foundation-philosopher

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

FAQPage Schema
How do I make better architecture decisions with a structured framework?

Apply the five-phase process: audit assumptions, decompose the problem with Five Whys root cause analysis, generate at least three alternatives, score them with a weighted trade-off matrix, and run a cognitive bias check before finalizing the decision record.

How to compare technology options like Redux vs Zustand objectively?

Use the weighted scoring method: define criteria such as learning curve, scalability, and performance, assign percentage weights totaling 100, score each option 1-10 per criterion, and compute composite scores. Document the accepted trade-offs and a review trigger.

When should I use first principles analysis versus skipping it?

Use the full framework for architecture changes and technology selection affecting many files. For simple bug fixes, skip it entirely; for feature additions, apply only the assumption, alternatives, and trade-off phases.

What cognitive biases affect technical decision-making?

The framework covers anchoring, confirmation bias, sunk cost fallacy, availability heuristic, and overconfidence. It provides detection questions and mitigations such as pre-mortem analysis, devil's advocate, and outside-view base rate checks.

How do I document a technical decision for future review?

Use the Strategic Decision Record template: capture context, examined assumptions with confidence levels, root cause chain, alternatives with scores, accepted trade-offs, bias check confirmation, success criteria, and a review trigger condition.