Use when comparing multiple named alternatives across several criteria, need transparent trade-off analysis, making group decisions requiring alignment, choosing between vendors/tools/strategies, stakeholders need to see decision rationale, balancing competing priorities (cost vs quality vs speed), user mentions "which option should we choose", "compare alternatives", "evaluate vendors", "trade-offs", or when decision needs to be defensible and data-driven.
View on GitHublyndonkl/claude
thinking-frameworks-skills
January 24, 2026
Select agents to install to:
npx add-skill https://github.com/lyndonkl/claude/blob/main/skills/decision-matrix/SKILL.md -a claude-code --skill decision-matrixInstallation paths:
.claude/skills/decision-matrix/# Decision Matrix ## What Is It? A decision matrix is a structured tool for comparing multiple alternatives against weighted criteria to make transparent, defensible choices. It forces explicit trade-off analysis by scoring each option on each criterion, making subjective factors visible and comparable. **Quick example:** | Option | Cost (30%) | Speed (25%) | Quality (45%) | Weighted Score | |--------|-----------|------------|---------------|----------------| | Option A | 8 (2.4) | 6 (1.5) | 9 (4.05) | **7.95** ← Winner | | Option B | 6 (1.8) | 9 (2.25) | 7 (3.15) | 7.20 | | Option C | 9 (2.7) | 4 (1.0) | 6 (2.7) | 6.40 | The numbers in parentheses show criterion score × weight. Option A wins despite not being fastest or cheapest because quality matters most (45% weight). ## Workflow Copy this checklist and track your progress: ``` Decision Matrix Progress: - [ ] Step 1: Frame the decision and list alternatives - [ ] Step 2: Identify and weight criteria - [ ] Step 3: Score each alternative on each criterion - [ ] Step 4: Calculate weighted scores and analyze results - [ ] Step 5: Validate quality and deliver recommendation ``` **Step 1: Frame the decision and list alternatives** Ask user for decision context (what are we choosing and why), list of alternatives (specific named options, not generic categories), constraints or dealbreakers (must-have requirements), and stakeholders (who needs to agree). Understanding must-haves helps filter options before scoring. See [Framing Questions](#framing-questions) for clarification prompts. **Step 2: Identify and weight criteria** Collaborate with user to identify criteria (what factors matter for this decision), determine weights (which criteria matter most, as percentages summing to 100%), and validate coverage (do criteria capture all important trade-offs). If user is unsure about weighting → Use [resources/template.md](resources/template.md) for weighting techniques. See [Criterion Types](#criterion-types) for