Systematically compare technologies, frameworks, and tools to guide technology selection decisions.
---
name: tech-stack-eval
description: When the user needs to choose between technologies, frameworks, or tools - or says "which framework should I use", "compare X vs Y", "should we migrate from X to Y", "what database should I use", "calculate TCO".
related: [architecture-design, cicd-setup]
reads: [startup-context]
---
# Tech Stack Evaluation
## When to Use
- Comparing frontend/backend frameworks or libraries for new projects
- Evaluating cloud providers (AWS vs Azure vs GCP) for specific workloads
- Planning technology migrations with risk and effort assessment
- Calculating TCO including hidden costs; making build vs. buy decisions
- Assessing open-source library viability and ecosystem health
Do NOT use when: the decision is trivial (use team preference), the technology is already mandated, or this is an emergency production issue.
## Context Required
From `startup-context`: product type, team skills, tech stack, stage, scale, budget. Also ask:
- What problem are you solving? (push back on solution-first thinking)
- Non-negotiable requirements (performance, compliance, team familiarity)
- Team experience with each option and timeline pressure (tight deadlines favor familiar tools)… load the full skill through Skill Me