research

Evaluate technology options and architectures with a structured research process.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/BoneTheDeveloper/Electronic-Contact-Contact-Book --skill research-bonethedeveloper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: research
Source: https://github.com/BoneTheDeveloper/Electronic-Contact-Contact-Book/tree/main/.claude/skills/research
Command: npx skills add https://github.com/BoneTheDeveloper/Electronic-Contact-Contact-Book --skill research-bonethedeveloper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a repeatable, evidence-based approach to identifying, evaluating, and selecting technology options and architectures, reducing guesswork and enabling informed design decisions across projects.

Core Features & Use Cases

  • Structured, phase-driven methodology (scope definition, information gathering, analysis, and reporting)
  • Multi-source research and evidence synthesis from official docs, benchmarks, and peer reviews
  • Architecture evaluation, risk/benefit analysis, and scalability/security considerations
  • Use Case: compare three technology stacks for a new web application and produce a decision-ready architecture brief

Quick Start

Initiate a focused teardown of three competing tech stacks for a given project and deliver a decision-ready architecture brief.

Frequently Asked Questions about research

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

FAQPage Schema
How do I evaluate technology options and architectures for software projects?

Architecture evaluation compares competing technology stacks by analyzing scalability, security, and risk-benefit factors to produce a decision-ready brief for software design.

What is the best way to compare technology stacks for a new web application?

Requirements gathering for architecture decisions involves defining scope, systematically gathering peer reviews and benchmark data, and analyzing options to generate actionable reporting.

How do I structure technology evaluation research to reduce guesswork?

Structure technology evaluation research through a phase-driven methodology covering scope definition, information gathering, analysis, and formal reporting to reduce guesswork and enable informed design.

Can I use this methodology for requirements gathering and best-practices research?

Technology research limitations arise when insufficient evidence exists; mitigate this by synthesizing official docs, benchmarks, and peer reviews to inform scalable and secure architecture decisions.