skills.rest
All-The-Vibes
All-The-VibesOFFICIAL
Explore all skills by this author →
GitHub

technical-research

Conduct systematic technical research and document findings with ADRs.

4|2|Updated Jan 10, 2026
Search Tags:#decision making#documentation#research#architecture decisions#technical evaluation#ADRs#POC
One-click install
npx skills add https://github.com/All-The-Vibes/skills-catalog --skill technical-research-all-the-vibes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: technical-research
Source: https://github.com/All-The-Vibes/skills-catalog/tree/main/.claude/skills/research/technical-research
Command: npx skills add https://github.com/All-The-Vibes/skills-catalog --skill technical-research-all-the-vibes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic technical research provides a repeatable framework to ask clear questions, compare options, and document evidence to support technology decisions.

Core Features & Use Cases

  • Define clear research questions for technology decisions and architectural choices.
  • Establish evaluation criteria and apply a consistent, evidence-based scoring approach.
  • Perform hands-on verification (POCs) and document findings with Architecture Decision Records (ADRs) to inform decisions.
  • Use Case: when evaluating new technologies, selecting libraries, or choosing between architectural patterns.

Quick Start

  1. Define the research question.
  2. List evaluation criteria across functional, non-functional, team, and operational dimensions.
  3. Gather 3-5 candidate technologies and run lightweight hands-on tests.
  4. Document findings, decisions, and rationale in ADRs.

Frequently Asked Questions about technical-research

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

FAQPage Schema
What is systematic technical research for evaluating new technologies?▼

Systematic technical research is a repeatable framework to define clear questions, compare options, and document evidence for technology decisions. It applies to evaluating new technologies, selecting libraries, and guiding architectural choices.

How do I document architectural decisions and technology evaluations?▼

You document architectural decisions by creating Architecture Decision Records (ADRs) that capture your research findings, decisions, and rationale. This ensures technology choices are backed by consistent, evidence-based scoring.

What's the best way to compare libraries and choose architectural patterns?▼

The best way to compare libraries is to define research questions, list evaluation criteria across functional and non-functional dimensions, gather 3-5 candidates, run lightweight hands-on tests, and document findings in ADRs.

How do I set up evaluation criteria for a technical evaluation?▼

Set up evaluation criteria by defining standards across functional, non-functional, team, and operational dimensions. Apply a consistent, evidence-based scoring approach to compare candidate technologies for your architectural decisions.

Do I need to run POCs when selecting a new technology stack?▼

You need to run lightweight hands-on POCs to perform verification during technical research. Testing 3-5 candidate technologies ensures your technology choices are informed by practical evidence rather than just theoretical documentation.

Related Skills

Explore More Education & Research Skills→
yu13130122297yu13130122297

scout

Identify uncertainties in research framing, datasets, metrics, and baselines.

Community
Intermediate
adolfoaranaes12adolfoaranaes12
2

create-adr

Create Architecture Decision Records with context, alternatives, rationale, and consequences.

Community
Advanced
abudhahirabudhahir

architecture-documenter

Generate system architecture documentation and Architecture Decision Records.

Community
Advanced
Dev10x-GuruDev10x-Guru
7

Dev10x:adr-evaluate

Orchestrate adversarial debates among agents to produce ranked ADR drafts.

Official
Advanced