Forge-Technology-Evaluation

Evaluate candidate technologies against weighted criteria and record selections as architecture decision records.

Updated Jul 18, 2026
One-click install
npx skills add https://github.com/Nealsch/ForgeOS --skill forge-technology-evaluation-nealsch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Forge-Technology-Evaluation
Source: https://github.com/Nealsch/ForgeOS/tree/main/Framework/05-Skills/02-Architecture/Forge-Technology-Evaluation
Command: npx skills add https://github.com/Nealsch/ForgeOS --skill forge-technology-evaluation-nealsch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Technology choices are often made on opinion or familiarity, then rationalized afterward. This Skill replaces ad-hoc selection with a disciplined evaluation process: criteria and weights are agreed before candidates are compared, evidence is gathered and traced, and the final decision is recorded durably as an Architecture Decision Record (ADR). ## Core Features & Use Cases - Criteria-First Evaluation: Elicit functional, quality-attribute, and organizational criteria, then agree weightings and thresholds with stakeholders before naming candidates. - Evidence-Based Comparison: Gather documented capabilities, benchmarks, licence terms, community health, and migration costs, then score candidates against weighted criteria with sensitivity analysis. - ADR Recording: Capture the recommendation, trade-offs, exit costs, and revisit triggers as an ADR for durable governance. - Use Case: During the Design phase, a Software Architect must choose between three database platforms. Use this Skill to define weighted criteria with the Product Owner, compare candidates including the incumbent baseline, and record the selection as an ADR. ## Quick Start Use the Forge-Technology-Evaluation skill to compare candidate databases for our new service against weighted criteria and record the recommendation as an ADR.

Frequently Asked Questions about Forge-Technology-Evaluation

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

FAQPage Schema
How do I evaluate technologies for an architecture decision?▼

Define the decision scope, agree weighted criteria and thresholds with stakeholders before naming candidates, gather evidence for each candidate including an incumbent baseline, score them against the criteria, and record the recommendation as an ADR with revisit triggers.

What is a weighted decision matrix for technology selection?▼

A weighted decision matrix scores each candidate technology against criteria that have been assigned importance weights agreed with stakeholders. The Skill also requires sensitivity analysis showing how the result changes if weights shift.

When should I use technology evaluation versus dependency analysis?▼

Use this evaluation process for architecturally significant selections such as platforms, frameworks, or databases. For small, low-reach library choices, use dependency-level vetting and coding standards instead.

Does this Skill mandate specific technologies or vendors?▼

No. The Skill is technology-independent by construction and defines only evaluation discipline. Any named technology is illustrative, and concrete selections are always project decisions recorded in ADRs.

Who approves the final technology selection?▼

The Skill produces a recommendation with trade-offs and risks, but the Product Owner disposes of the decision. The approved outcome is captured as an ADR with trigger conditions for revisiting it.