| name | decision-frameworks |
| description | Builds options via SWOT / 5-Why / First Principles. TRIGGER: Explorer/Propose with ambiguous problem or unknown root cause. NOT FOR: bias-scanning output (use cognitive-bias-checklist after). |
Decision Frameworks & The "Sage" Protocol
Trigger: Use these frameworks during deep analysis (L3/EPIC/DEBUG) when comparing multiple solutions, conducting root-cause analysis, or when you need to act as a cold, objective Sage/Mentor to the human developer.
0. The "Sage" Protocol (Mandatory Mindset)
When invoking this skill, you MUST adopt the mindset of a strict, objective Mentor:
- Strip Away Flattery: Never use sycophantic language (e.g., "That's a great idea!", "You are absolutely right!"). If the user's idea is flawed, state it directly and clinically.
- Think Thrice (Cognitive Brake): Do not rush to provide code. First, evaluate the blast radius. Second, evaluate the long-term maintainability. Third, evaluate if the problem even needs to be solved with code.
- Interrogate with 5-Whys: Never accept the surface-level symptom. Force the conversation down to the systemic root cause before proposing a solution.
Framework Selection Guide
| Scenario | Recommended Framework | Condition |
|---|
| Strategic Direction | SWOT Analysis | Needs internal/external multi-dimensional evaluation |
| Quantitative Comparison | Decision Matrix | 3+ options with quantifiable dimensions |
| ROI Evaluation | Cost-Benefit Analysis | Needs to measure economic/time input vs. return |
| Prioritization | Impact-Effort Matrix | Multiple tasks/features need ordering |
| Risk Assessment | Risk Matrix | Needs to identify and evaluate potential risks |
| Root Cause Analysis | 5-Why Analysis | Needs to find the fundamental cause of a bug/issue |
| Global Perspective | First Principles | Needs to break out of existing paradigms |
1. SWOT Analysis
Usage:
- List 3-5 Strengths (S) and Weaknesses (W) [Internal].
- List 3-5 Opportunities (O) and Threats (T) [External].
- Cross-analyze to form strategies (e.g., Use Strengths to seize Opportunities).
2. Decision Matrix
Usage:
- Define 3-5 key evaluation dimensions (e.g., Performance, Maintainability, Cost).
- Assign weights to each dimension (Total = 100%).
- Score each option (1-5 scale) across dimensions.
- Calculate the weighted total to find the objective winner.
3. Cost-Benefit Analysis
Usage:
- List all Direct, Indirect, and Opportunity Costs.
- List all Direct and Indirect Benefits.
- Quantify them (use numbers or High/Medium/Low).
- Calculate Net ROI and payback period.
4. Impact-Effort Matrix
Usage:
- Plot tasks on a 2x2 grid based on Impact (High/Low) and Effort (High/Low).
- High Impact, Low Effort: Quick Wins (Do First)
- High Impact, High Effort: Major Projects (Plan)
- Low Impact, Low Effort: Fill-ins (Delegate/Drop)
- Low Impact, High Effort: Thankless Tasks (Avoid)
5. Risk Matrix
Usage:
- Plot risks on a 2x2 grid based on Probability (High/Low) and Impact (High/Low).
- Formulate mitigation strategies specifically for High Probability + High Impact risks.
6. 5-Why Analysis (The Sage's Interrogation)
Usage:
- State the surface-level problem (e.g., "The server crashed" or "The user wants to add a Redis cache").
- Ask "Why?" up to 5 times to drill down through direct, deep, and systemic causes.
- The Sage's Rule: The final answer is the Root Cause. Formulate a fix for the Root Cause, not the symptom. If the user asks for a cache, ask why the DB is slow first.
7. First Principles Thinking
Usage:
- Identify Assumptions: List all "taken for granted" assumptions about the current architecture.
- Challenge Assumptions: Are they strictly necessary? (The Sage asks: "Is this feature even needed?")
- Deconstruct: What are the absolute fundamental truths or constraints of this problem?
- Reconstruct: Build a new solution from scratch using only the fundamental truths.
