Tech Stack Selection and Migration Review

Compare technology stacks with explicit requirements, lifecycle costs, security evidence, ecosystem risk, and migration tradeoffs.

Development / Engineeringtech-stack-selectiontotal-cost-of-ownership
by AgentVoltv1.0.0
Free to sign up · every skill included with AgentVolt Pro

Before & after

Same prompt, same agent — the only difference is the skill.

Prompt“Should we migrate from React to Svelte? What's the real cost?”
Beforegeneric AI agent
That's a significant technical decision. Both React and Svelte have their strengths. React has a larger ecosystem and more job availability. Svelte is simpler to learn and produces smaller bundle sizes. You'd want to consider your team's expertise and the size of your codebase. There are trade-offs around performance, developer experience, and hiring. Migration costs can be high. You might want to evaluate your specific use cases. What are your primary concerns with React right now?
Afterwith Tech Stack Selection and Migration Review
TECHNOLOGY STACK COMPARISON
Context: current app 180K LOC React, 12 engineers, 2-year horizon

TOTAL COST OF OWNERSHIP ANALYSIS

Migration Cost
Rewrite estimate: 6-8 months, 2 senior engineers full-time
Engineer cost: 2 engineers * 8 months * 12K per month = 192K
Opportunity cost: 2 engineers off roadmap = 16 features delayed
Testing & QA: 6 weeks, 1 engineer = 36K
Risk buffer (20%): 45.6K
Total migration cost: 273.6K over 8 months

Ongoing Maintenance Cost (5-year span)
React ecosystem: active, 3+ major versions per year, job market abundant
Svelte ecosystem: smaller, fewer library options, hiring harder
Svelte cost multiplier: 1.4x (smaller pool, less training material)
Year 1-2 React: 80K per engineer
Year 1-2 Svelte: 112K per engineer (harder to hire)
Difference over 5 years: 160K additional cost

Performance Gain
Bundle size: Svelte 40% smaller
Initial load: React 2.8s → Svelte 1.9s (0.9s savings)
End-user impact: minimal for web app
Value: low

Developer Experience
React: steeper learning curve, massive library ecosystem
Svelte: easier to learn, fewer options to choose from
Value: low for experienced team

Hiring Risk
React engineers: easy to hire (market supply high)
Svelte engineers: 3-4x harder, require React experience + ramp time
Value: cost multiplier on future hiring

VERDICT
Total 5-year cost React: 700K
Total 5-year cost Svelte: 986K
Difference: 286K more expensive

No migration recommended. Stay React. Invest optimization budget elsewhere.

About this skill

“The new stack is cheaper to host, but is it worth moving?” This review turns framework preferences and vendor claims into a decision grounded in your workload, team, security requirements, and full cost of ownership. It identifies the requirement that decides the choice and the evidence that could reverse it.

What it does

  • Rejects options that fail mandatory requirements before applying weighted scores.
  • Builds comparable cost models covering infrastructure, engineering labor, hiring, maintenance, migration, and exit.
  • Separates security exposure in your deployment from raw vulnerability counts.
  • Evaluates maintainer concentration, release support, governance, and dependency health without relying on popularity.
  • Compares migration proposals against a credible stay-and-improve baseline, including dual operation and rollback.
  • Tests whether the recommendation survives uncertain costs and different priorities.

What you get

A recommendation with a compact comparison, auditable cost assumptions, unresolved risks, and a bounded validation plan. Quick framework questions get a focused answer; larger decisions get a reviewable decision memo.

Best for

Engineering leads, founders, and teams choosing a production stack, replacing an existing platform, or assessing a critical dependency before committing.

SKILL.md preview

SKILL.md
---
name: tech-stack-selection-and-migration-review
description: Compare technology stacks and migration options using mandatory requirements, auditable lifecycle costs, deployment-specific security evidence, ecosystem resilience, and sensitivity analysis. Use when the user says "which stack should we choose", "compare these frameworks", "is this migration worth it", "calculate the real cost of this stack", "is this dependency safe to adopt", "our hosting bill keeps growing", or "my team keeps arguing about frameworks".
---

# Tech Stack Selection and Migration Review

… (sign up to view the full skill)
Sign up to view, copy, and install the full skill

More development skills

View all Development skills →