technology-radar

Govern technology choices across Adopt, Trial, Assess, and Hold rings.

86|9|Updated Jun 5, 2026
One-click install
npx skills add https://github.com/magnus919/hermes-profiles --skill technology-radar-magnus919
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: technology-radar
Source: https://github.com/magnus919/hermes-profiles/tree/main/skills/technology-radar
Command: npx skills add https://github.com/magnus919/hermes-profiles --skill technology-radar-magnus919

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The Technology Radar provides a structured approach for evaluating, approving, and governing technology choices to balance risk, speed, and long-term platform health.

Core Features & Use Cases

  • Architecture governance: Establish standards, RFC/ARB processes, and decision records to keep technology aligned with business goals.
  • Build vs buy and TCO analysis: Systematically evaluate procurement versus in-house development for sustainable velocity.
  • Radar lifecycle and metrics: Track technologies across Adopt/Trial/Assess/Hold rings with DORA/SPACE-aligned dashboards to surface investments and deprecations.
  • Use Case: When selecting a new tool for a microservice or migrating a legacy stack, run a radar review to categorize it and document actioned decisions.

Quick Start

Run a quarterly radar review to categorize technologies, document RFC-driven decisions, and publish the governance artifacts.

Frequently Asked Questions about technology-radar

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

FAQPage Schema
What is a technology radar and how does it balance risk with innovation?

A technology radar is a structured framework to evaluate and govern technology choices, balancing risk, speed, and platform health. It standardizes decision-making across architecture reviews and vendor evaluations using Adopt, Trial, Assess, and Hold rings.

How do I standardize architecture governance and document build vs buy decisions?

Standardize architecture governance by enforcing an ADR/RFC process to document decisions. Systematically evaluate build versus buy options through total cost of ownership analysis to ensure technology aligns with business goals and maintains sustainable velocity.

How do you run a quarterly radar lifecycle review for microservice technology selection?

Run a quarterly radar review to categorize technologies into Adopt, Trial, Assess, or Hold rings. Document RFC-driven decisions and publish governance artifacts to guide product technology roadmaps and standardize tool selection for microservices.

Can engineering metrics like DORA and SPACE be integrated into technology governance?

Yes, DORA and SPACE metrics are integrated into the radar lifecycle through aligned dashboards. These engineering metrics surface investments and deprecations, tracking platform health and technology adoption progress during architecture reviews.

When should I use an RFC-driven architecture review board for vendor evaluations?

Use an RFC-driven architecture review board when selecting new tools or migrating legacy stacks to systematically evaluate procurement. It enforces decision records and total cost of ownership analysis to keep technology aligned with business goals.

What are the limitations of using a technology radar for platform health tracking?

The framework requires strict adherence to a quarterly radar lifecycle and RFC governance to function effectively. Without consistent architecture reviews and DORA/SPACE metrics integration, technology categorization and deprecation tracking may lose accuracy.