moai-foundation-philosopher

Standardize strategic software decisions with assumption capture, first-principles analysis, and weighted trade-off scoring.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured framework to guide strategic decision-making in software projects, enabling teams to reason more clearly and avoid common biases.

Core Features & Use Cases

  • Structured decision process: Document assumptions, perform first-principles analysis, and conduct trade-off evaluations.
  • Bias mitigation: Integrate cognitive-bias checks and pre-mortem analyses into decision workflows.
  • MoAI workflow integration: Aligns with SPEC-style planning and risk assessment practices for architecture and technology choices.
  • Use Case: When facing a complex architectural decision, apply the Philosopher Framework to surface assumptions, compare options, and record the rationale for future audits.

Quick Start

Run the MoAI planner to activate the Philosopher Framework:

  • /moai:1-plan to start a SPEC-style analysis
  • /moai:2-run to apply the chosen trade-offs during implementation

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 architectural decisions to avoid cognitive bias in software projects?

Structure architectural decisions by documenting assumptions, applying first-principles analysis, and embedding cognitive-bias checks within your workflow. This ensures strategic software choices are evaluated through root-cause decomposition rather than intuition.

What is the best way to perform trade-off analysis for technology selection?

Perform trade-off analysis for technology selection by evaluating options with weighted scores and capturing underlying assumptions. Comparing choices through structured root-cause decomposition yields a clear rationale for future audits.

How do I apply first principles to system design and risk assessment?

Apply first principles to system design by decomposing complex problems into fundamental truths and assessing risks from the ground up. This structured approach surfaces hidden assumptions and standardizes strategic decision-making.

Can I use this framework for organizational change and product development scenarios?

Yes, you can use this framework for organizational change and product development scenarios. It standardizes strategic decision-making across system design and risk assessment by integrating pre-mortem analyses and bias mitigation.

How do I start a SPEC-style analysis for complex software architecture choices?

Start a SPEC-style analysis by running the MoAI planner to activate the Philosopher Framework. This initiates the process to capture assumptions, evaluate trade-offs, and record the rationale for your architecture choices.

When should I not use a structured decision framework for software engineering?

Avoid using a structured decision framework for trivial or fully deterministic engineering choices. It is designed for complex scenarios requiring trade-off evaluations, risk assessment, and cognitive-bias mitigation, where documenting assumptions adds value.