What do I need to use Tech Radar?

Team or company name; Current tech stack; Technologies under active evaluation; Technologies to deprecate or move off; Strategic technology bets; Team context.

Is Tech Radar free to use?

Yes — run it free in the browser playground (no API key needed for the sponsored trial, or bring any provider key), or install it into Claude Code, Cursor, ChatGPT and more via npx pm-claude-skills. MIT-licensed and open source.

Tech Radar

Q: How do I know the Tech Radar output is good?

The skill verifies itself against its own quality checks: Every blip has a written rationale paragraph — not just a table row entry; The decision trail is populated with at least the initial placement date for every blip; Hold-ring entries include a concrete migration path or target technology, not just "stop using it"; Ring definitions are present and include both what each ring means AND what engineers should do in response.

🔵 Stable🕐 updated 2026-06-08 🔷 SkillSpec L3 pm-engineering

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.

▶ Run it free — no key needed 📝 Grade your existing draft View SKILL.md ↗

What to give it

▸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 deliberate bet on (e.g., "we're all-in on Kubernetes" or "migrating to event-driven architecture")

▸Team context — team size, product domain, and any constraints (regulatory, compliance, vendor lock-in concerns) If a technology is mentioned without a ring placement, use the rationale inputs to determine the appropriate ring. When uncertain between two rings, ask.

✅ The bar it holds itself to

Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.

✓Every blip has a written rationale paragraph — not just a table row entry

✓The decision trail is populated with at least the initial placement date for every blip

✓Hold-ring entries include a concrete migration path or target technology, not just "stop using it"

✓Ring definitions are present and include both what each ring means AND what engineers should do in response

✓Maintenance process includes: nomination channel, review cadence, who decides, and ring-change criteria

✓Technologies identified as "strategic bets" in the inputs are placed in Adopt (if proven) or Trial (if being rolled out)

✓Technologies identified for deprecation are in Hold with a rationale that references the replacement

⚠️ What it refuses to do

Do not place a technology in Adopt without evidence it is proven at the team's scale — aspirational placements mislead engineers

Do not add a blip without a written rationale paragraph — table rows without context are unusable

Do not create a Hold entry without specifying a concrete migration path or target technology

Do not skip the maintenance process — a radar with no process for updates becomes stale within two quarters

Do not omit ring definitions — engineers need to know what they should do in response to each ring, not just what the ring means

Install

npx pm-claude-skills add --agent claude   # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcp

Start with

Related skills

🔌 Embed this skill

Drop this on your blog, docs, or site — it renders a "Run this skill" card:

<div data-pm-skill="tech-radar"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>

💬 Discussion

Tech Radar is one of 1174 open-source professional AI agent skills — all SkillSpec L3. Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog