tech-trend-watch

Aggregate State of JS, State of CSS, and Thoughtworks Radar data to identify migration risks.

320|3|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/mizchi/skills --skill tech-trend-watch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-trend-watch
Source: https://github.com/mizchi/skills/tree/main/tooling/tech-trend-watch
Command: npx skills add https://github.com/mizchi/skills --skill tech-trend-watch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Annual technology stack oversight that helps teams stay aligned with evolving JS/CSS tools and Thoughtworks Radar, enabling timely migration planning and risk reduction.

Core Features & Use Cases

  • Inventory current stack by cataloging dependencies from package.json and key tooling signals; map findings to external benchmarks (State of JS, State of CSS, and Thoughtworks Radar).
  • Evaluate maturity and adoption signals to categorize items as STABLE, EMERGING, or LEGACY for P0/P1 migration decisions.
  • Produce an actionable stack-review document that guides migration planning, budgeting, and governance cycles.

Quick Start

Run the annual tech-trend-watch review to generate the stack health report.

Frequently Asked Questions about tech-trend-watch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I conduct an annual technology stack review for migration planning?

To conduct an annual technology stack review, aggregate dependency signals from your package.json and map them against external benchmarks like State of JS to identify LEGACY items needing migration. This categorizes your stack into STABLE, EMERGING, or LEGACY tiers.

What is a tech radar review and when do I need it for my software stack?

A tech radar review evaluates your software stack's maturity and adoption signals against industry benchmarks like Thoughtworks Radar. You need it to identify platform health risks, reduce tooling vulnerabilities, and plan timely vendor migrations.

How do I evaluate State of JS and State of CSS data to identify legacy framework risks?

Evaluate State of JS and State of CSS data by mapping your current dependencies against adoption and maturity signals from these reports. This process categorizes your tools to highlightLEGACY frameworks requiring P0/P1 migration decisions and timeline planning.

Can I use this tech-trend-watch review for backend and tooling ecosystems, or is it only for front-end?

You can use this review for backend and tooling ecosystems as well as front-end. It applies to software engineering teams responsible for platform health across front-end, backend, and tooling ecosystems, mapping all dependencies to external benchmarks.

What is the best way to prioritize stack migration actions and timelines?

The best way to prioritize stack migration actions is to score maturity and adoption signals, categorizing items as STABLE, EMERGING, or LEGACY. This produces an actionable stack-review document with prioritized P0/P1 actions and timelines.

What limitations exist when aggregating State of CSS and Thoughtworks Radar data for stack health reports?

A key limitation is that generating a stack health report requires predefined data sources and a scoring matrix. Without providing specific tooling signals and benchmark inputs, the review cannot output an actionable migration plan document.