research-synthesis

Synthesize research on frameworks and tools into a decision memo.

3|4|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/jamestorrevillas/dev-skills --skill research-synthesis-jamestorrevillas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: research-synthesis
Source: https://github.com/jamestorrevillas/dev-skills/tree/main/.github/skills/research-synthesis
Command: npx skills add https://github.com/jamestorrevillas/dev-skills --skill research-synthesis-jamestorrevillas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamline technology decisions by researching multiple sources, synthesizing findings, and documenting clear recommendations to guide engineering teams.

Core Features & Use Cases

  • Structured research workflow: follow DEFINE, GATHER, EVALUATE, SYNTHESIZE, DECIDE, DOCUMENT to produce reproducible results.
  • Framework & tech comparison: evaluate multiple options across fit, maturity, ecosystem, and cost with a consolidated decision memo.
  • Executive summaries & stakeholder briefs: generate concise, decision-ready reports for non-technical stakeholders.
  • Template-driven decision documentation: capture context, options, rationale, trade-offs, and revisit conditions.

Quick Start

Provide a structured tech-stack comparison for your next project and output a decision memo.

Frequently Asked Questions about research-synthesis

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

FAQPage Schema
How do I synthesize technical research to inform framework and tool decisions?

To synthesize technical research for framework decisions, follow a structured workflow: define requirements, gather sources, evaluate options, synthesize findings, decide, and document. This produces a reproducible decision memo capturing context, trade-offs, and rationale.

What is the best way to compare technology options across maturity and ecosystem fit?

The best way to compare technology options is to evaluate multiple frameworks across fit, maturity, ecosystem, and cost. Consolidating these evaluation criteria into a structured decision memo ensures clear technology choices and stakeholder alignment.

How do I document technology evaluation trade-offs for non-technical stakeholders?

Document technology evaluation trade-offs for stakeholders by generating concise, decision-ready executive summaries. These briefs distill complex framework comparisons and architectural rationale into actionable recommendations tailored for non-technical audiences.

When do I need a structured decision template for software architecture choices?

You need a structured decision template for software architecture choices when evaluating multiple frameworks or tools. It captures context, options, rationale, trade-offs, and revisit conditions, ensuring reproducible technology decisions and clear documentation.

Can I use this research synthesis workflow for any software project tech stack comparison?

Yes, you can use this research synthesis workflow for any software project tech stack comparison. It scopes technology evaluations across frameworks, tools, and architectures, guiding engineering teams from initial research to documented recommendations.