research-analyst

Turn broad technical questions into structured investigations with evidence-backed conclusions.

22|2|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/jshsakura/awesome-opencode-skills --skill research-analyst-jshsakura
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: research-analyst
Source: https://github.com/jshsakura/awesome-opencode-skills/tree/main/skills/research-analyst
Command: npx skills add https://github.com/jshsakura/awesome-opencode-skills --skill research-analyst-jshsakura

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a disciplined framework to convert broad technical questions into structured, decision-ready investigations with explicit evidence quality, reducing ambiguity and enabling actionable conclusions.

Core Features & Use Cases

  • Structured investigation workflow: define the investigation question, constraints, and objective to keep scope tight.
  • Evidence-first synthesis: gather high-quality sources, separate observed facts from inference, and annotate confidence levels.
  • Actionable output: deliver a structured findings summary with caveats, risks, and clear next steps for decision-makers.
  • Use cases: technology evaluations, design questions, architecture decisions, and research planning for software projects.

Quick Start

Initiate a structured investigation by defining the question, context, and decision objective, then produce a decision-ready report with evidence quality, uncertainties, and recommended next steps.

Frequently Asked Questions about research-analyst

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

FAQPage Schema
How do I structure technical research for a software architecture decision?▼

Structured technical research for software architecture decisions requires defining the investigation question, gathering high-quality sources, and separating observed facts from inferences to deliver decision-ready findings with annotated confidence levels.

What is the best way to evaluate technology implementation approaches with evidence?▼

Evaluating technology implementation approaches with evidence involves an evidence-first synthesis workflow that gathers high-quality sources, explicitly separates facts from inference, and annotates confidence levels to reduce ambiguity for decision-makers.

How do I handle uncertainty and evidence quality in product strategy research?▼

Handling uncertainty in product strategy research requires explicitly annotating confidence levels, separating observed facts from inference, and delivering structured findings summaries with caveats, risks, and clear next steps to drive actionable conclusions.

Can I use this structured investigation workflow for research planning?▼

Yes, the structured investigation workflow supports research planning by defining the investigation question, constraints, and objective to keep scope tight, then producing a decision-ready report with evidence quality and recommended next steps.

What separates fact from inference in a decision-ready technical investigation?▼

Separating fact from inference in a decision-ready technical investigation involves gathering high-quality sources, explicitly distinguishing observed facts from inferred conclusions, and annotating confidence levels to ensure structured findings reduce ambiguity.

When do I need a structured research workflow for technical topics?▼

You need a structured research workflow for technical topics when broad questions require evidence-backed conclusions, such as technology evaluations, design questions, architecture decisions, and research planning where ambiguity must be reduced for clear decision-making.