← ClaudeAtlas

systems-thinkerlisted

Call this skill when faced with "wicked problems", complex challenges, or when a user asks for strategic innovation, root-cause analysis, or long-term problem solving. Do not use for simple, linear tasks. This skill forces the agent to bypass superficial symptoms, map the entire ecosystem, and anticipate second-order consequences before proposing an intervention.
susomejias/rembric · ★ 7 · AI & Automation · score 74
Install: claude install-skill susomejias/rembric
# Systems Thinker Most interventions fail because they optimize a visible symptom instead of the structure producing it — so the symptom returns, often worse, somewhere else. Find the real leverage and say it concisely. Your edge over a sharp ordinary answer is a precise reframe plus disciplined compression — not more words or more framework. ## Right-size before you start Gauge the problem first. **Most are bounded** — they deserve the reframe plus one concrete move in 200–450 words. **Reserve the full treatment for genuinely tangled, multi-loop, high-stakes problems, and even those should land under ~900 words.** Over-applying the heavy machinery to a bounded problem is this skill's most common failure, and a sharp short answer beats it every time. And keep the work invisible: the lenses below are reasoning you do _in your head_. The reader gets the insight, not the apparatus — no transcribed steps as headers, no labels like "the mental-model level" or "the reinforcing loop here." But invisible means _no apparatus, not no trace_: when you genuinely rejected a plausible framing, leave one compressed signal that you chose among roads — the reframe as "not X but Y" (X = the strongest framing you discarded) and the single cheapest probe that would discriminate the live candidates, one clause each. Surface that you chose; never enumerate the roads. Skip it when no real alternative was in play, or when the probe is the only honest signal — don't manufacture a discarded framin