technical-research

Evaluate technologies with defined criteria and document decisions in ADRs.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/datorresb/vibecoding-starter --skill technical-research-datorresb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: technical-research
Source: https://github.com/datorresb/vibecoding-starter/tree/main/.claude/skills/research/technical-research
Command: npx skills add https://github.com/datorresb/vibecoding-starter --skill technical-research-datorresb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured methodology to evaluate technologies, libraries, and architectural options, enabling evidence-based decisions.

Core Features & Use Cases

  • Structured questions and criteria definition
  • Systematic candidate evaluation with documented results
  • Hands-on verification (POC) and ADR-backed decisions

Quick Start

Run a technical research session by defining a clear decision question, establishing evaluation criteria, and outlining a plan for hands-on validation; then generate an ADR documenting the decision.

Frequently Asked Questions about technical-research

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

FAQPage Schema
How do I evaluate technologies for architectural decisions?▼

Evaluating technologies for architectural decisions requires defining clear research questions, establishing evaluation criteria, and conducting hands-on verification. This systematic tech research approach ensures evidence-based decisions are documented using an Architecture Decision Record (ADR).

What is an Architecture Decision Record and when do I need one?▼

An Architecture Decision Record (ADR) documents technical research and evidence-based decisions. You need an ADR when making architectural decisions, selecting technologies, or comparing libraries to ensure evaluation criteria, hands-on verification, and decision rationale are systematically recorded.

How do I compare libraries and select the right one for my software project?▼

Comparing libraries requires defining clear evaluation criteria and conducting systematic candidate evaluation. Perform hands-on verification through a Proof of Concept (POC) to validate technology selection, then document the evidence-based decision to ensure the right choice for your software project.

Does this structured tech research approach work for vendor assessments?▼

Structured tech research supports vendor assessments across software projects by applying defined evaluation criteria and hands-on verification. This systematic candidate evaluation process ensures vendor selection is evidence-based and properly documented through an Architecture Decision Record (ADR).

What are the limitations of relying on a POC for technology selection?▼

A Proof of Concept (POC) for technology selection requires integration into a structured methodology. Without clear research questions, defined evaluation criteria, and systematic candidate evaluation, hands-on verification alone may yield incomplete evidence, leading to poorly documented architectural decisions.