create-tech-radar

Create BYOR tech radar entries with Hugo frontmatter and content body.

Updated Feb 14, 2025
One-click install
npx skills add https://github.com/pwarnock/pwarnock.github.io --skill create-tech-radar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-tech-radar
Source: https://github.com/pwarnock/pwarnock.github.io/tree/main/.claude/skills/create-tech-radar
Command: npx skills add https://github.com/pwarnock/pwarnock.github.io --skill create-tech-radar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to consistently create BYOR-compliant tech radar entries, turning abstract technology assessments into structured, actionable guidance.

Core Features & Use Cases

  • Opinionated analysis of technology candidates to guide adoption decisions.
  • Structured frontmatter generation for Hugo content bundles (title, description, quadrant, ring, tags).
  • Workflow guidance from initial evaluation to formal radar entry creation, including optional references and assets.

Quick Start

Provide the technology name, description, quadrant, and ring to generate a new tech radar entry.

Frequently Asked Questions about create-tech-radar

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

FAQPage Schema
What is a tech radar entry and when do I need one for technology evaluation?

Tech radar entries turn abstract technology assessments into structured, actionable adoption guidance. You need them to consistently evaluate technology candidates across product, engineering, and operations contexts from initial assessment to adoption decision.

How do I create a BYOR tech radar entry with Hugo frontmatter?

To create a BYOR tech radar entry, provide the technology name, description, quadrant, and ring. This generates a Hugo bundle with structured frontmatter, optional tags, and a descriptive body for technology evaluation documentation.

What frontmatter fields are enforced for a Hugo tech radar bundle?

Enforced frontmatter fields for a Hugo tech radar bundle include title, description, quadrant, and ring. Optional tags and a descriptive content body are also generated to provide additional context for the technology evaluation.

Can I use this approach for technology adoption decisions across operations and engineering?

Yes, this tech radar entry approach applies to technology evaluation scenarios for adoption decisions across product, engineering, and operations contexts, ranging from initial assessment to formal radar entry creation.

What is the best way to document an engineering tool adoption decision in a tech radar?

The best way to document an engineering tool adoption decision is generating an opinionated tech radar entry with BYOR. This enforces structured frontmatter for quadrant and ring placement, ensuring consistent, actionable evaluation guidance.