Can I analyze just one specific area of my system?

Yes, you can use specialized subcommands like 'explain-system-latency-tradeoffs' or 'explain-system-consistency-tradeoffs' to focus on a single architectural dimension.

How does the skill find architectural evidence?

It scans API contracts, configuration files (like quorum rules), and operational signatures (like SLO definitions and retry policies) to find hard commitments and real-world runtime behaviors.

What are the six tradeoff axes analyzed by this skill?

The skill analyzes Consistency & Availability, Latency & Throughput, Data Distribution, Transaction Boundaries, Resilience & Failure Isolation, and Observability/Security/Cost.

Why does the skill use parallel subagents?

For full system audits, it launches six concurrent subagents to provide a faster and more specialized deep-dive into each axis, allowing for a comprehensive synthesis of complex system tensions.

System Tradeoff Architect

Name: System Tradeoff Architect
Author: florianbuetow

byflorianbuetow

•

Analytics & Monitoring

Analyzes codebases and infrastructure configurations to reverse-engineer distributed system tradeoffs and identify architectural risks.

This skill provides an automated, evidence-based audit of distributed systems by scanning source code, deployment manifests, and configuration files. It evaluates architectural decisions across six critical axes—including consistency, latency, data distribution, and resilience—using a tiered evidence model. By deploying parallel subagents to deep-dive into specific design patterns like CAP theorem positioning or circuit breaker configurations, it helps developers understand whether their system's actual behavior aligns with its intended design and highlights hidden operational risks or accidental defaults.

Key Features

01Evidence-based audits across three tiers of confidence (Commitments, Mechanisms, Signatures)

02Structured risk reporting with severity levels and actionable recommendations

03Identification of misaligned configurations and accidental design choices

044 GitHub stars

05Multi-axis analysis of consistency, availability, latency, and throughput

06Parallel subagent execution for deep, concurrent architectural evaluations

Use Cases

01Identifying performance bottlenecks and throughput-latency tradeoffs in microservices

02Auditing a legacy distributed system to understand its actual CAP theorem positioning

03Reviewing resilience patterns and failure isolation strategies before a major production launch

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add florianbuetow/claude-code explain-system-tradeoffs

For use in Claude.ai and ChatGPT

Download Skill