systems-feedback-mapping

Identify reinforcing and balancing feedback loops in causal maps.

212|23|Updated May 23, 2026
One-click install
npx skills add https://github.com/human-avatar/skills-for-humanity --skill systems-feedback-mapping
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: systems-feedback-mapping
Source: https://github.com/human-avatar/skills-for-humanity/tree/main/skills/systems-feedback-mapping
Command: npx skills add https://github.com/human-avatar/skills-for-humanity --skill systems-feedback-mapping

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you identify why a system keeps behaving the same way—such as oscillating, overshooting, or collapsing—by making reinforcing and balancing feedback loops explicit.

Core Features & Use Cases

  • Feedback loop identification: Converts vague symptoms like “it keeps happening” into named reinforcing (+) and balancing (−) loops.
  • Causal mapping with polarity: Builds a variable-to-variable causal link map that labels whether effects amplify or counteract.
  • Delay-aware diagnosis: Surfaces delays that commonly cause overshoot and oscillation, then identifies the dominant loop driving current behavior.

Quick Start

Run systems-feedback-mapping when you need to map the feedback loops behind an outcome like “why do we keep overshooting and then fall back?”

Frequently Asked Questions about systems-feedback-mapping

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

FAQPage Schema
How do I identify reinforcing and balancing feedback loops in a causal map?

Feedback loop identification involves mapping variable-to-variable causal links with assigned polarities to trace reinforcing and balancing loops. By checking negative-link parity and marking delays, you can determine the dominant loop driving system oscillation or overshoot.

Why does my system keep overshooting and then falling back?

Overshoot and fall-back behaviors are typically caused by delays within balancing feedback loops. By explicitly marking delays during causal mapping and determining the dominant loop, you can diagnose why the system fails to stabilize and correct the unintended consequences.

What is the best way to map system dynamics delays that cause oscillation?

Mapping system dynamics delays requires building a causal map with explicit delay marking across defined stocks and flows. This delay-aware diagnosis identifies the dominant loop responsible for oscillation within your system boundary and time horizon.

Can I use causal mapping for complex engineered systems with defined boundaries?

Causal mapping applies to complex engineered systems by defining a specific boundary and time horizon. You select variables, assign causal polarity, trace loops with negative-link parity, and determine dominant loops for actionable diagnosis of unintended consequences.

How do I determine the dominant feedback loop driving current system behavior?

Determining the dominant feedback loop requires tracing reinforcing and balancing loops using negative-link parity and marking explicit delays. This identifies which loop primarily drives current system behavior, enabling actionable diagnosis of overshoot or oscillation.