write-tech-radar

Draft technology radar entries with ring recommendations, trade-offs, and MADR-linked adoption guidance.

Updated Feb 10, 2026
One-click install
npx skills add https://github.com/vesviet/agent-skills --skill write-tech-radar-vesviet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-tech-radar
Source: https://github.com/vesviet/agent-skills/tree/main/core/skills/documentation/write-tech-radar
Command: npx skills add https://github.com/vesviet/agent-skills --skill write-tech-radar-vesviet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often make technology adoption decisions informally, losing the context, trade-offs, and evidence behind them. This Skill produces concise, decision-oriented technology radar entries that answer "should my team use this, and under what conditions?" with enforced governance gates. ## Core Features & Use Cases - Standardized Ring Classification: Assigns technologies to the four ThoughtWorks rings (Adopt, Trial, Assess, Caution) with enforced sign-off gates for Caution entries and time-bounded Assess phases. - Evidence Discipline: Separates POC-only claims from production-verified evidence, validates vendor claims against primary sources, and links every entry to a MADR-format ADR. - AI Tool Tracking: Maintains a dedicated AI tools quadrant with mandatory bi-annual re-evaluation and data-flow classification. - Use Case: A platform team evaluating a new service mesh drafts a radar entry summarizing context, trade-offs, and a Trial recommendation, linked to the binding ADR, so future teams understand the decision without re-interviewing stakeholders. ## Quick Start Use the write-tech-radar skill to draft a radar entry assessing whether our team should adopt OpenTelemetry for observability.

Frequently Asked Questions about write-tech-radar

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

FAQPage Schema
How do I write a technology radar entry?▼

Define the technology decision scope, gather evidence on strengths, risks, and alternatives, then draft an entry with a title, ring recommendation, rationale, and adoption guidance. Link the entry to a MADR-format ADR and keep wording concise and decision-oriented.

What are the standard ThoughtWorks technology radar rings?▼

The four standard rings are Adopt, Trial, Assess, and Caution. Custom names like Hold or Avoid break organizational radar consistency and are rejected. Caution entries require Architecture Board or Technical Lead sign-off before adoption.

What is the difference between a tech radar entry and an ADR?▼

A radar entry is a navigation aid giving directional adopt/hold/trial guidance, while an ADR in MADR format is the binding decision record. Every radar entry representing a significant shift must link to its underlying ADR for full decision lineage.

How should AI tools be tracked on a technology radar?▼

AI tools belong in a dedicated quadrant or sub-radar with rings explicitly applied, re-evaluated at minimum bi-annually. Entries must classify the tool's data handling with data-classification.yaml and surface the data flow honestly.

When should a technology not be placed in the Assess ring?▼

Assess is inappropriate when no measurable POC success criteria or deadline can be defined, since it becomes a permanent parking lot. Every Assess entry must declare an ISO 8601 deadline and concrete evaluation criteria.