Technology Radar
Evaluate and track technology choices on a radar. Use when selecting frameworks, databases, or tools.
Install
/plugin marketplace add sethdford/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sethdford/claude-skills --skill technology-radargit clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/architect/decision-making/skills/technology-radar ~/.claude/skills/technology-radarPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Technology Radar Systematically evaluate technologies and track them on a radar (Adopt, Trial, Assess, Hold) to manage technology portfolio. ## Context You are evaluating technologies. Establish a technology radar as organizational consensus on what to use, experiment with, evaluate, or avoid. ## Domain Context Based on Thoughtworks Technology Radar and tech governance: - **Adopt**: Use for new projects; well-proven, low risk - **Trial**: Experiment in bounded contexts; promising but unproven at scale - **Assess**: Evaluate before committing; interesting but uncertain - **Hold**: Don't use; superceded or risky ## Instructions 1. **Assess Technology**: Maturity, support, community, performance, cost, learning curve 2. **Plot on Radar**: Where does it belong? 3. **Define Transition**: How to move from Trial to Adopt (or obsolete)? 4. **Communicate**: Publish radar; align team on tech direction ## Anti-Patterns - **Adopting Too Quickly**: Use new shiny tech before proven. Result: regret. **Guard**: New tech starts in Assess/Trial. - **Radar Never Updates**: Published once, ignored after. **Guard**: Review quarterly. ## Further Reading - _Thoughtworks Technology Radar_ — published tri-annually - _Technology Strategy Books_ by various authors
Details
- Skill name
technology-radar- Repository
- sethdford/claude-skills
- Path
architect/decision-making/skills/technology-radar/SKILL.md- License
- MIT
- Repo updated
- 11 March 2026
FAQ
What does the Technology Radar skill do?
Evaluate and track technology choices on a radar. Use when selecting frameworks, databases, or tools.
How do I install the Technology Radar skill?
Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Technology Radar popular?
It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.
Related skills
A B Test Design
48sethdford/claude-skills
Design rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.
A B Test Design Pm
48sethdford/claude-skills
Analytics and experimentation skill for product managers.
Abuse Case Design
48sethdford/claude-skills
Design abuse cases (negative use cases) showing how attackers misuse system features. Use when identifying attacks that exploit intended functionality or business logic flaws.
Threat Library
48sethdford/claude-skills
Build and maintain a reusable threat library tailored to your organization, platform, and threat landscape. Use when cataloging threats for future analyses, threat modeling sessions, and architecture reviews.
Systematic Debugging
48sethdford/claude-skills
Disciplined methodology to isolate bugs through hypothesis-driven testing. Form hypotheses, test them with minimal changes, narrow scope systematically. Use when bugs are unclear or reproduce intermittently.
Weighted Scoring
48sethdford/claude-skills
Create custom weighted prioritization frameworks aligned to your strategy.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.