approach-evaluation

Name: approach-evaluation
Availability: InStock
Author: petrsimonidesxart

Evaluate technical approaches against project constraints with documented evidence.

Updated Mar 8, 2026

Search Tags:#comparison #evidence #decision-support #evaluate #architectural #industry-standards #approaches

Ready to run

npx skills add https://github.com/petrSimonidesXart/xPmGateway --skill approach-evaluation-petrsimonidesxart

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: approach-evaluation
Source: https://github.com/petrSimonidesXart/xPmGateway/tree/main/.gaai/core/skills/cross/approach-evaluation
Command: npx skills add https://github.com/petrSimonidesXart/xPmGateway --skill approach-evaluation-petrsimonidesxart

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured, evidence-based evaluation of multiple approaches to a technical or architectural problem, enabling informed decision-making without prescribing a chosen solution.

Core Features & Use Cases

Industry standards research and context gathering
Identification of 2-3 viable approaches (including the obvious)
Structured comparison against project criteria with traceable evidence
Documentation of trade-offs and open questions, without making a decision

Quick Start

Input the problem statement and project context to generate a formal approach-evaluation document.

Frequently Asked Questions about approach-evaluation

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

FAQPage Schema

How do I evaluate different architectural approaches for a software project?▼

To evaluate architectural approaches, input your problem statement and project context to generate a formal evaluation document that compares 2-3 viable options against defined criteria using traceable industry evidence.

What is an evidence-based approach evaluation in software engineering?▼

An evidence-based approach evaluation is a structured comparison of technical solutions that researches industry standards, documents mechanisms and trade-offs, and records limitations without enforcing a final architectural decision.

Can I use this to compare technical solutions without committing to a final decision?▼

Yes, this approach evaluation explicitly documents structured comparisons, trade-offs, and open questions against project constraints without enforcing a final decision, leaving the ultimate choice to the user.

How do I document trade-offs and limitations for competing architectural patterns?▼

You document trade-offs and limitations by gathering project context, researching current industry standards, and producing a formal evaluation artifact that records the mechanisms and constraints of each viable approach.

What's the best way to research industry standards for architectural decision-making?▼

The best way to research industry standards for architectural decision-making is to establish evaluation criteria from project context, then collect traceable evidence for 2-3 viable approaches to form a structured comparison.

How many viable approaches should I include in an architectural comparison?▼

You should include 2-3 viable approaches, including the obvious choice, in an architectural comparison to ensure a structured evaluation against project constraints and industry standards.