name: technology-advisor
description: Systematic technology selection using the STRIDE framework (Scope, Test reversibility, Requirements, Identify options, Deep evaluation, Execute). Use when selecting databases, frameworks, cloud providers, languages, or any technical stack decisions. Matches evaluation rigor to decision reversibility -- lightweight for 2-way doors, thorough for 1-way doors. Produces weighted decision matrices with sensitivity analysis.
Technology Advisor
Guide systematic technology selection using the STRIDE framework. Match evaluation rigor to decision reversibility.
When to Use
- "Help me pick/choose/select [technology]"
- "Should I use X or Y?"
- "What [database/framework/cloud] should I use?"
- "Recommend a [technology type]"
- Validating or reviewing past technology choices
Core Principle
Match rigor to reversibility:
- 2-way door (reversible): 1-3 days, lightweight evaluation
- 1-way door (irreversible): 1-2 weeks, full STRIDE process
The STRIDE Framework
S - Scope the Decision
T - Test for Reversibility
R - Requirements Definition
I - Identify & Screen Options
D - Deep Evaluation
E - Execute & Validate
S - Scope (15-30 min)
Questions to ask:
- What technology are we selecting? (database, framework, cloud, etc.)
- What problem does this solve?
- Who are the stakeholders?
- What's the time horizon? (6 months, 2 years, 5+ years)
T - Test Reversibility (5 min)
Reversibility factors:
| Factor |
Easy to reverse |
Hard to reverse |
| Migration cost |
<5% of effort |
>25% of effort |
| Data portability |
Easy export |
Proprietary lock-in |
| Team retraining |
<1 week |
>1 month |
| Time to switch |
<2 weeks |
>2 months |
Assessment:
- 2-way door -> "Reversible. Use lightweight 3-day evaluation (Steps S,T,R,E)"
- 1-way door -> "Hard to reverse. Use full STRIDE (2 weeks)"
R - Requirements (1-2 hours)
COMPRIS -- 7 universal criteria:
| # |
Criterion |
Description |
| C |
Cost |
Total cost of ownership |
| O |
Operational |
Deployment complexity, support burden |
| M |
Maintainability |
Documentation, debugging, code quality |
| P |
Performance |
Speed, scalability, resource efficiency |
| R |
Risk |
Vendor stability, security, compliance, lock-in |
| I |
Integration |
API compatibility with existing systems |
| S |
Skills |
Team expertise, learning curve, hiring availability |
Weight criteria by normalizing 1-5 importance ratings to percentages (sum = 100%).
I - Identify & Screen (2-4 hours)
- Generate options -- research 10-20 initial candidates
- Apply hard filters -- budget ceiling, platform support, compliance, maturity
- Present shortlist -- narrow to 3-5 finalists
D - Deep Evaluation (4-8 hours)
Score each option 1-5 per criterion:
- 5 = Excellent / Far exceeds
- 4 = Good / Exceeds
- 3 = Average / Meets
- 2 = Below average / Partially meets
- 1 = Poor / Does not meet
Decision matrix:
| Criterion |
Weight |
Option A |
Option B |
Option C |
| Cost |
25% |
4 (1.00) |
3 (0.75) |
5 (1.25) |
| Performance |
20% |
5 (1.00) |
4 (0.80) |
3 (0.60) |
| Skills |
15% |
3 (0.45) |
5 (0.75) |
2 (0.30) |
| TOTAL |
100% |
3.45 |
3.30 |
3.15 |
Sensitivity analysis: Test if winner changes with different weight distributions or +/-1 score variations on uncertain criteria.
E - Execute & Validate
Document the decision:
- Problem statement
- Shortlist evaluated
- Criteria & weights
- Scores & rationale
- Final recommendation
- Risks & mitigations
- Success metrics
- Review date
Interaction Patterns
Full guidance: Walk through all 6 STRIDE steps for complex decisions.
Quick assist: User provides context upfront. Focus on criteria weights, score options, present recommendation.
Second opinion: User has a choice, needs validation. Review their logic, test sensitivity, identify blind spots.
Decision review: Reassess a past decision against original success metrics.
Anti-Patterns to Prevent
| Pattern |
Response |
| Analysis paralysis |
"We've been evaluating 2 weeks on a reversible decision. Pick one, validate with 3-day prototype." |
| Premature commitment |
"This is a 1-way door. Spend 2 weeks evaluating, not 2 days." |
| Feature-list syndrome |
"Both have 90% of features. Focus on the 3 criteria that differentiate them." |
| Recency bias |
"HackerNews loves [new tech] but it has 500 stars. [Mature option] has 50K stars and proven stability." |
| Sunk cost fallacy |
"2 months invested, but signals say it's wrong. Migration is 3 weeks. Sunk cost is not a reason to continue." |
Key Principles
- Match rigor to reversibility -- don't over-analyze reversible choices
- Requirements before options -- define needs before researching solutions
- Weights reveal priorities -- if user can't weight criteria, priorities are unclear
- Data over opinions -- score based on benchmarks, not marketing
- Document decisions -- future you needs to know why you chose this
- Set review dates -- technology landscape changes, reassess periodically
References
- Source: claude-skills/technology-advisor (MIT License)
- STRIDE framework for systematic technology evaluation
1---2name: technology-advisor-33description: <!-- AUTO-GENERATED by export-skills.py — DO NOT EDIT -->4---5<!-- AUTO-GENERATED by export-skills.py — DO NOT EDIT -->6---7name: technology-advisor8description: Systematic technology selection using the STRIDE framework (Scope, Test reversibility, Requirements, Identify options, Deep evaluation, Execute). Use when selecting databases, frameworks, cloud providers, languages, or any technical stack decisions. Matches evaluation rigor to decision reversibility -- lightweight for 2-way doors, thorough for 1-way doors. Produces weighted decision matrices with sensitivity analysis.9---1011# Technology Advisor1213Guide systematic technology selection using the STRIDE framework. Match evaluation rigor to decision reversibility.1415## When to Use1617- "Help me pick/choose/select [technology]"18- "Should I use X or Y?"19- "What [database/framework/cloud] should I use?"20- "Recommend a [technology type]"21- Validating or reviewing past technology choices2223## Core Principle2425**Match rigor to reversibility:**26- **2-way door** (reversible): 1-3 days, lightweight evaluation27- **1-way door** (irreversible): 1-2 weeks, full STRIDE process2829## The STRIDE Framework3031```32S - Scope the Decision33T - Test for Reversibility34R - Requirements Definition35I - Identify & Screen Options36D - Deep Evaluation37E - Execute & Validate38```3940### S - Scope (15-30 min)4142Questions to ask:431. What technology are we selecting? (database, framework, cloud, etc.)442. What problem does this solve?453. Who are the stakeholders?464. What's the time horizon? (6 months, 2 years, 5+ years)4748### T - Test Reversibility (5 min)4950Reversibility factors:5152| Factor | Easy to reverse | Hard to reverse |53|---|---|---|54| Migration cost | <5% of effort | >25% of effort |55| Data portability | Easy export | Proprietary lock-in |56| Team retraining | <1 week | >1 month |57| Time to switch | <2 weeks | >2 months |5859Assessment:60- **2-way door** -> "Reversible. Use lightweight 3-day evaluation (Steps S,T,R,E)"61- **1-way door** -> "Hard to reverse. Use full STRIDE (2 weeks)"6263### R - Requirements (1-2 hours)6465**COMPRIS -- 7 universal criteria:**6667| # | Criterion | Description |68|---|---|---|69| C | Cost | Total cost of ownership |70| O | Operational | Deployment complexity, support burden |71| M | Maintainability | Documentation, debugging, code quality |72| P | Performance | Speed, scalability, resource efficiency |73| R | Risk | Vendor stability, security, compliance, lock-in |74| I | Integration | API compatibility with existing systems |75| S | Skills | Team expertise, learning curve, hiring availability |7677Weight criteria by normalizing 1-5 importance ratings to percentages (sum = 100%).7879### I - Identify & Screen (2-4 hours)80811. **Generate options** -- research 10-20 initial candidates822. **Apply hard filters** -- budget ceiling, platform support, compliance, maturity833. **Present shortlist** -- narrow to 3-5 finalists8485### D - Deep Evaluation (4-8 hours)8687Score each option 1-5 per criterion:88- **5** = Excellent / Far exceeds89- **4** = Good / Exceeds90- **3** = Average / Meets91- **2** = Below average / Partially meets92- **1** = Poor / Does not meet9394**Decision matrix:**9596| Criterion | Weight | Option A | Option B | Option C |97|---|---|---|---|---|98| Cost | 25% | 4 (1.00) | 3 (0.75) | 5 (1.25) |99| Performance | 20% | 5 (1.00) | 4 (0.80) | 3 (0.60) |100| Skills | 15% | 3 (0.45) | 5 (0.75) | 2 (0.30) |101| **TOTAL** | **100%** | **3.45** | **3.30** | **3.15** |102103**Sensitivity analysis:** Test if winner changes with different weight distributions or +/-1 score variations on uncertain criteria.104105### E - Execute & Validate106107Document the decision:108- Problem statement109- Shortlist evaluated110- Criteria & weights111- Scores & rationale112- Final recommendation113- Risks & mitigations114- Success metrics115- Review date116117## Interaction Patterns118119**Full guidance:** Walk through all 6 STRIDE steps for complex decisions.120121**Quick assist:** User provides context upfront. Focus on criteria weights, score options, present recommendation.122123**Second opinion:** User has a choice, needs validation. Review their logic, test sensitivity, identify blind spots.124125**Decision review:** Reassess a past decision against original success metrics.126127## Anti-Patterns to Prevent128129| Pattern | Response |130|---|---|131| **Analysis paralysis** | "We've been evaluating 2 weeks on a reversible decision. Pick one, validate with 3-day prototype." |132| **Premature commitment** | "This is a 1-way door. Spend 2 weeks evaluating, not 2 days." |133| **Feature-list syndrome** | "Both have 90% of features. Focus on the 3 criteria that differentiate them." |134| **Recency bias** | "HackerNews loves [new tech] but it has 500 stars. [Mature option] has 50K stars and proven stability." |135| **Sunk cost fallacy** | "2 months invested, but signals say it's wrong. Migration is 3 weeks. Sunk cost is not a reason to continue." |136137## Key Principles1381391. **Match rigor to reversibility** -- don't over-analyze reversible choices1402. **Requirements before options** -- define needs before researching solutions1413. **Weights reveal priorities** -- if user can't weight criteria, priorities are unclear1424. **Data over opinions** -- score based on benchmarks, not marketing1435. **Document decisions** -- future you needs to know why you chose this1446. **Set review dates** -- technology landscape changes, reassess periodically145146## References147148- Source: claude-skills/technology-advisor (MIT License)149- STRIDE framework for systematic technology evaluation150151<!-- Source: .faos/custom/skills/architecture/technology-advisor/SKILL.md -->