# Thinking Systems

When behavior is emergent across components, fixes elsewhere break, loops/delays...

- Repository: https://github.com/tjboudreaux/cc-thinking-skills (1690 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-08-07
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add tjboudreaux/cc-thinking-skills --skill thinking-systems -g -a claude-code -y`
Codex: `npx skills add tjboudreaux/cc-thinking-skills --skill thinking-systems -g -a codex -y`
Cursor: `npx skills add tjboudreaux/cc-thinking-skills --skill thinking-systems -g -a cursor -y`
Gemini CLI: `npx skills add tjboudreaux/cc-thinking-skills --skill thinking-systems -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add tjboudreaux/cc-thinking-skills`

## Description

When behavior is emergent across components, fixes elsewhere break, loops/delays dominate, map boundary, stocks/flows, feedback, archetypes, then rank leverage.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Systems Mapping and Leverage

Treat the problem as structure and interaction, not isolated parts. Map boundary, stocks/flows, loops/delays, and recurring patterns; intervene at the highest feasible leverage after a side-effect check.

## When to Use

- Symptom spans services/components; single-stack fixes fail or bounce.
- A change in one place breaks another; behavior is emergent.
- Problem recurs despite local fixes (structure, not only symptom).
- Need to rank interventions when parameter/buffer tweaks do not stick.

## When NOT to Use

- Single-component linear bug with clear stack/diff, trace and fix.
- Throughput limited by one obvious stage, use theory-of-constraints.
- Decision is a consequence chain of one proposed action, use second-order.
- Approach selection (plan vs probe vs stabilize), use cynefin first.

## Procedure

The rest: https://github.com/tjboudreaux/cc-thinking-skills/blob/HEAD/skills/thinking-systems/SKILL.md