evaluative-research

Compare technology options and produce evidence-based recommendations.

Updated Oct 8, 2025
One-click install
npx skills add https://github.com/ichabodcole/project-docs-scaffold-template --skill evaluative-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: evaluative-research
Source: https://github.com/ichabodcole/project-docs-scaffold-template/tree/main/plugins/project-docs/skills/evaluative-research
Command: npx skills add https://github.com/ichabodcole/project-docs-scaffold-template --skill evaluative-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This methodology provides a structured approach to evaluate options, compare technologies, and make evidence-based decisions between alternatives.

Core Features & Use Cases

  • Phase 1: Define the Decision — articulate the decision, drivers, constraints, context, and stakeholders.
  • Phase 2: Landscape Scan — identify candidates, quick-filter, categorize, and select finalists (2-4) for deep evaluation.
  • Phase 3: Deep Evaluation — hands-on assessment, codebase fit, effort estimates, risk assessment, and long-term trajectory; for each option document description, strengths, weaknesses, effort, and risk.
  • Phase 4: Comparative Analysis — build a weighted decision matrix and articulate key trade-offs; produce a formal recommendation.
  • Output: A structured investigation narrative, including a recommended path and conditions for reconsideration.

Quick Start

Provide a decision topic and 2–4 viable options to compare, and have Evaluative Research generate a structured analysis and recommendation.

Frequently Asked Questions about evaluative-research

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

FAQPage Schema
How do I make evidence-based technology selections for a framework migration?

Evidence-based technology selections require defining decision drivers, scanning the landscape, and evaluating 2-4 finalists. You compare options using a weighted decision matrix to produce a formal recommendation with documented context and risk assessment.

What is a landscape scan and when do I need one for architecture decisions?

A landscape scan identifies candidate technologies, quick-filters them, and selects finalists for deep evaluation. You need one for architecture decisions when comparing multiple libraries, frameworks, or services to ensure a comprehensive evidence-based selection.

How do I compare technology options using a weighted decision matrix?

To compare technology options, evaluate each against defined criteria such as codebase fit, effort estimates, and risk. Build a weighted decision matrix to articulate key trade-offs, yielding a formal recommendation and conditions for reconsideration.

Can I use this approach to evaluate both libraries and architectural approaches?

Yes, you can evaluate both libraries and architectural approaches. This methodology applies broadly to technology selections across product, platform, or engineering projects, covering migrations, frameworks, and services.

What is the best way to document technology risk assessment and trade-offs?

The best way to document risk assessment is through a structured investigation narrative. It captures the decision context, comparative analysis of key trade-offs, the recommended path, and explicit conditions for future reconsideration.

How many technology options should I shortlist for a deep comparative analysis?

You should shortlist 2-4 viable options for deep comparative analysis. This allows thorough hands-on assessment of codebase fit, effort estimates, and long-term trajectory without overwhelming the decision-making process.