skills.rest
calvyntwh
calvyntwhCOMMUNITY
Explore all skills by this author →
GitHub

systems-thinking

Analyze feedback loops in distributed systems to identify reinforcing and balancing dynamics.

Updated Mar 31, 2026
Search Tags:#architecture#post-mortem#resilience#scaling#systems-thinking#system-dynamics#feedback-loops
One-click install
npx skills add https://github.com/calvyntwh/karu-custom-skills --skill systems-thinking-calvyntwh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systems-thinking
Source: https://github.com/calvyntwh/karu-custom-skills/tree/main/skills/systems-thinking
Command: npx skills add https://github.com/calvyntwh/karu-custom-skills --skill systems-thinking-calvyntwh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Systems-thinking identifies hidden dependencies, feedback loops, and delay effects that cause architectural changes to produce unexpected side effects, helping teams avoid cascade failures and resource exhaustion.

Core Features & Use Cases

  • Loop identification: Trace nodes and edges to discover reinforcing, balancing, and delay-heavy loops that affect system behavior.
  • Validation & pre-mortem: Use log analysis and trade-off questions to verify assumptions before deploying changes.
  • Use cases: Architecture migrations, scaling decisions (10x traffic), performance tuning, post-mortems, and adding services that touch shared resources.

Quick Start

Run systems-thinking to analyze the feedback loops and likely second-order effects of increasing the thread pool size in the payments service.

Frequently Asked Questions about systems-thinking

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

FAQPage Schema
What is systems thinking in distributed system architecture?▼

Identify reinforcing and balancing feedback loops in distributed system architecture to predict cascade failures and resource exhaustion. Tracing node connections and classifying loops reveals hidden dependencies before changes are deployed.

How do I analyze feedback loops before a major scaling decision?▼

Trace node connections and validate assumptions with log analysis to identify delay-heavy and reinforcing loops before scaling. This prevents unexpected side effects and resource exhaustion during major traffic increases.

Can I use feedback loop analysis for post-mortems and performance tuning?▼

Yes, feedback loop analysis supports post-mortems and performance tuning by classifying balancing dynamics and tracing distributed system connections. It identifies root causes of cascade failures and resource bottlenecks.

What's the best way to identify hidden dependencies in architecture migrations?▼

Trace node edges and analyze logs to discover delay-heavy loops, validating trade-off assumptions to prevent unexpected second-order effects. This identifies hidden dependencies before deploying architecture migrations.

Why do architectural changes cause resource exhaustion and cascade failures?▼

Architectural changes cause cascade failures due to hidden delay-heavy feedback loops and balancing dynamics. Identifying these reinforcing loops through log analysis and node tracing prevents unexpected resource exhaustion.

Related Skills

Explore More Software Engineering Skills→
sQVesQVe

debug-issue

Diagnose bugs by tracing evidence and generating a BR issue template.

Community
Advanced
viktorbezdekviktorbezdek
10

trade-off-analysis

Analyze product option trade-offs and produce a trade-off matrix with costs and kill conditions.

Community
Intermediate
arbazkhan971arbazkhan971
26

chaos

Automate resilience testing of distributed systems with structured chaos experiments.

Community
Advanced
cyberkaidacyberkaida
797

ctf-rev

Analyze CTF binaries to extract flags through structured reverse engineering.

Community
Advanced