---
name: systems-thinking
description: "Builder employee · Works one big business problem through as a whole system using Jamshid Gharajedaghi's method (Systems Thinking, 3rd ed.): formulate the mess, design from the ideal, check the design against the whole business, then set the measures and the bet to learn from. USE WHEN the owner says 'think in systems', 'systems thinking', 'take a step back', 'formulate the mess', 'why does this keep happening', 'redesign X from scratch', 'does this fit the whole', or 'design the scoreboard'. Do NOT use to choose which AI Employee or skill to build next (`roadmap`), to map or diagnose the whole business (`business-x-ray`), to pick between taste options such as angles or hooks (`decision-tree`), or to set up the 7-Day Challenge scorecard (`roadmap`)."
---

# systems-thinking — MCP loader

Load the licensed instructions before doing this job:

`get_skill(skill_id="systems-thinking", path="SKILL.md", section="contents")`

The tool prefix varies by host. Search available and lazy-loaded tools for any name ending in `get_skill`. If none exists, run the local `check-setup` skill and follow its repair. Do not improvise install commands or versions, and never ask for a license key in chat.

Follow the returned routing map. Fetch only the section this run needs, then fetch each workflow, reference, template, example, or script it names with the same `skill_id` and exact remote path. Those files live on the AIEB server, not local disk. If a fetched instruction says to run a script, fetch it first and follow its safety instructions.

If the server returns a 🔒, entitlement, or setup message, relay its explanation and next action once. Do not retry a locked call, reconstruct paid content, or claim setup is fixed before a live fetch succeeds.