trade-off-analysis

Evaluates architectural alternatives using weighted decision matrices and ATAM trade-off analysis.

Updated Jun 28, 2026
One-click install
npx skills add https://github.com/JaviMontano/claude-plugins --skill trade-off-analysis-javimontano
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trade-off-analysis
Source: https://github.com/JaviMontano/claude-plugins/tree/main/plugins/claude-native-toolkit/skills/trade-off-analysis
Command: npx skills add https://github.com/JaviMontano/claude-plugins --skill trade-off-analysis-javimontano

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Architectural and technology decisions are often made on gut feeling or biased toward a predetermined winner, leaving teams without a defensible rationale when trade-offs between quality attributes like performance, cost, and maintainability must be justified. ## Core Features & Use Cases - Weighted Decision Matrices: Scores at least three alternatives against stakeholder-validated weighted criteria, producing explicit trade-off pairs ("chose X over Y because Z"). - ATAM Method: Applies Architecture Tradeoff Analysis Method with quality attribute scenarios (stimulus, response, measure) to surface sensitivity points and risks. - Uncertainty Modeling: Uses three-point/PERT estimates, Expected Monetary Value, and Monte Carlo simulation with P80 commitments when inputs are uncertain. - Use Case: A team choosing between three database architectures for availability, latency, and cost gets a scored decision matrix, an Architecture Decision Record, a risk catalog, and a sensitivity analysis showing whether the ranking survives plausible weight changes. ## Quick Start Ask the assistant to run a trade-off analysis comparing your architectural options with weighted criteria and produce an ADR with a defensible recommendation.

Frequently Asked Questions about trade-off-analysis

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

FAQPage Schema
How do I compare architecture options with a weighted decision matrix?▼

Define the decision, list at least three alternatives, and identify quality attributes like performance, cost, and maintainability. Stakeholders validate criterion weights, each option is scored with supporting evidence, and trade-off pairs are documented explicitly.

What is ATAM and when should I use it for architecture decisions?▼

ATAM (Architecture Tradeoff Analysis Method) evaluates architectural approaches against quality attribute scenarios with stimulus, response, and measure. Use it when decisions involve competing quality attributes and you need to identify sensitivity points and risks.

How do I make decisions when cost and duration estimates are uncertain?▼

Model uncertainty instead of using point estimates: apply three-point/PERT estimates, Expected Monetary Value for risky options, and Monte Carlo simulation for interacting inputs. Commit to the P80 outcome rather than the mean.

When should I not use a trade-off analysis or decision matrix?▼

Skip the matrix when a binding standard mandates a single answer, such as a required TLS version, since there are no real alternatives to score. Fabricating options for an authoritative requirement produces artificial analysis.

How do I avoid bias toward a predetermined winner in decision analysis?▼

Require stakeholder-validated weights rather than assumed ones, demand evidence for every score, and run sensitivity analysis to test whether plausible weight changes flip the ranking. A recommendation that flips easily is flagged as not robust.