sysdesign-tradeoff-framing

Articulate architectural tradeoffs and record decisions in a structured ADR format.

Updated Apr 23, 2026

Search Tags:#adr #risk-management #system-design #architecture-decision #tradeoffs #nfr #decision-record

Ready to run

npx skills add https://github.com/danilods/matilha-sysdesign-pack --skill sysdesign-tradeoff-framing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sysdesign-tradeoff-framing
Source: https://github.com/danilods/matilha-sysdesign-pack/tree/main/skills/sysdesign-tradeoff-framing
Command: npx skills add https://github.com/danilods/matilha-sysdesign-pack --skill sysdesign-tradeoff-framing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Articulates and records explicit architectural tradeoffs to prevent hand-waving decisions.

Core Features & Use Cases

Enforces a structured ADR workflow for two options and ties decisions to NFR priorities.
Documents the binding constraint and explicit reasoning to create a replayable decision.
Produces an ADR that preserves rejected options for future context and establishes a revisit trigger.

Quick Start

Draft an ADR that states the decision between two options, lists what each gives and costs, cites the relevant NFR priorities, and includes a revisit trigger.

Frequently Asked Questions about sysdesign-tradeoff-framing

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

FAQPage Schema

How do I document system design tradeoffs to prevent hand-waving architecture decisions?▼

To document system design tradeoffs, articulate explicit architectural options and record them using an Architecture Decision Record (ADR) format that captures per-option costs and benefits to prevent hand-waving decisions.

What is an ADR format that aligns architectural decisions with NFR priorities?▼

An ADR format aligned with NFR priorities includes a decision sentence, per-option gives and costs, a binding constraint, cited non-functional requirements, and a revisit trigger to ensure replayable architectural reasoning.

How to write an architecture decision record for scalability and availability tradeoffs?▼

Write an architecture decision record by framing two viable options across domains like scalability, availability, latency, and cost, then document the binding constraint and explicit reasoning to create a replayable decision.

When do I need to cite NFR priorities in a system design tradeoff decision?▼

You need to cite NFR priorities in a system design tradeoff decision whenever you are choosing between at least two viable options, ensuring the binding constraint reflects your non-functional requirement priorities.

Does this approach to architectural tradeoffs preserve rejected options for future context?▼

Yes, this approach to architectural tradeoffs produces an ADR that preserves rejected options for future context and establishes a revisit trigger to re-evaluate the decision when conditions change.

What should an architecture decision record include to make a replayable system design choice?▼

To make a replayable system design choice, an architecture decision record should include a decision sentence, per-option gives and costs, a binding constraint, cited NFR priorities, and a revisit trigger.