tradeoff-analysis

Document architectural decision trade-offs in a YAML risks-and-tradeoffs artifact.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/Burburton/amazing-specialists --skill tradeoff-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tradeoff-analysis
Source: https://github.com/Burburton/amazing-specialists/tree/main/templates/pack/full/.opencode/skills/architect/tradeoff-analysis
Command: npx skills add https://github.com/Burburton/amazing-specialists --skill tradeoff-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture decisions are often contested and poorly documented; this skill provides structured trade-off analyses to capture alternatives, criteria, and rationale.

Core Features & Use Cases

  • Identify and compare multiple viable approaches for a given decision point.
  • Capture risks, trade-offs, and mitigation strategies in a standard artifact.
  • Produce a clear revisitable record to support reviews, audits, and onboarding.

Quick Start

Run a trade-off analysis for a chosen decision and produce a ready-to-review risks-and-tradeoffs artifact.

Frequently Asked Questions about tradeoff-analysis

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

FAQPage Schema
How do I document architecture decisions and trade-offs for a technology selection?

To document architecture decisions, you capture alternatives, selection criteria, and risks in a structured YAML artifact. This risks-and-tradeoffs record includes the decision point, selected approach, and revisit triggers to support audits and onboarding.

What is the best way to compare alternatives during a system refactor?

Comparing alternatives during a system refactor involves evaluating viable approaches against defined criteria and capturing mitigation strategies. The output is a standard artifact that clarifies choices and justifies major architectural changes.

When do I need a structured trade-off analysis for architectural decisions?

You need a structured trade-off analysis during design phases for technology selections, refactors, and major system changes. It resolves contested architecture decisions by producing a clear, revisitable record.

Can I use this approach to capture risks and mitigation strategies for major system changes?

Yes, you can capture risks and mitigation strategies for major system changes by identifying trade-offs across multiple viable approaches. The process outputs a YAML artifact containing alternatives considered, selected approach, and revisit triggers.

Does the trade-off analysis output a standard format for architecture reviews?

Yes, the trade-off analysis outputs a YAML risks-and-tradeoffs artifact for architecture reviews. It contains structured fields including decision point, alternatives considered, selected approach, and revisit trigger to support audits.