tech-radar
Build a technology radar for an engineering team, categorizing technologies into Adopt/Trial/Assess/Hold quadrants following the ThoughtWorks Tech Radar format. Use when asked to create a tech radar, evaluate the team's technology landscape, categorize tools and frameworks, or establish a technology strategy. Produces a full tech radar with quadrant tables, individual blip rationales, a decision trail, and a maintenance process guide.
Profile →npx skills add majiayu000/claude-skill-registry --skill tech-radar --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Tech Radar Produce a complete technology radar document for an engineering team. The radar gives the team a shared, explicit position on every significant technology in their stack — what to standardize on, what to experiment with, what to evaluate, and what to actively stop using. Follow the ThoughtWorks Tech Radar format: four quadrants (Techniques, Tools, Platforms, Languages & Frameworks) each with four rings (Adopt, Trial, Assess, Hold). Each technology entry ("blip") gets a ring assignment, a one-paragraph rationale, and a date. Include a decision trail showing what moved and why, and a maintenance process the team can run to keep the radar current. ## Required Inputs Ask for these if not already provided: - **Team or company name** — for the document header - **Current tech stack** — list every significant technology, tool, language, and platform the team currently uses - **Technologies under active evaluation** — tools or frameworks the team is currently trying or considering - **Technologies to deprecate or move off** — anything the team wants to stop using or is actively migrating away from - **Strategic technology bets** — any technologies the company has made a delibe
- Required Inputs
- Output Format
- How to Read This Radar
- Quadrant 1: Techniques
- Adopt
- Trial
- Assess
- Hold
- Quadrant 2: Tools
- Quadrant 3: Platforms
- Quadrant 4: Languages & Frameworks
- Decision Trail
- Radar Maintenance Process
- Who Contributes
What does the tech-radar skill do?
Build a technology radar for an engineering team, categorizing technologies into Adopt/Trial/Assess/Hold quadrants following the ThoughtWorks Tech Radar format. Use when asked to create a tech radar, evaluate the team's technology landscape, categorize tools and frameworks, or establish a technology strategy. Produces a full tech radar with quadrant tables, individual blip rationales, a decision trail, and a maintenance process guide.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill tech-radar --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.