think-causal-layered-analysis
Produces a four-layer matrix (litany, system, worldview, myth) of the current 'used future' beside a reconstructed preferred future per layer, anchored by a deliberately changed deep metaphor. Use when an issue is stuck because the framing is stuck, the official account and the system explanation have been argued to exhaustion, and the real disagreement is about clashing worldviews and the unexamined story underneath. Not a single-cause diagnosis (that is think-iceberg-model) and not a forecast.
product-on-purpose · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add product-on-purpose/thinking-framework-skills --skill think-causal-layered-analysis技能说明
name: think-causal-layered-analysis description: Produces a four-layer matrix (litany, system, worldview, myth) of the current 'used future' beside a reconstructed preferred future per layer, anchored by a deliberately changed deep metaphor. Use when an issue is stuck because the framing is stuck, the official account and the system explanation have been argued to exhaustion, and the real disagreement is about clashing worldviews and the unexamined story underneath. Not a single-cause diagnosis (that is think-iceberg-model) and not a forecast. license: Apache-2.0 metadata: id: thinking-framework-skills.causal-layered-analysis family: systems-and-consequences evidence-tier: "C" version: 0.1.0 standard: "0.8"
Causal Layered Analysis
Most contested issues are argued at the surface and the system level - the headline numbers and the policy fixes - long after that argument has stopped being productive, because the real disagreement lives in clashing worldviews and an unexamined story underneath. Causal Layered Analysis (CLA) reads an issue at four vertical depths and then rebuilds it. It descends through the litany (the official, visible, unquestioned account), the system (the structural and short-term causes the litany rests on), the worldview (the deeper ideological and paradigmatic assumptions, and whose worldview is privileged), and the myth/metaphor (the unconscious, emotive, civilizational story underneath, carried in a guiding metaphor). The durable move is not the descent alone. It is to treat the issue as a text with competing readings rather than one true cause, and then to move back up and reconstruct - rewrite the deep metaphor into a new one and propagate a transformed worldview, system, and litany that follow from it. The output is a four-layer matrix that holds the current "used future" reading of each layer beside a reconstructed preferred-future reading of each layer, anchored by a deliberately changed deep metaphor. Its purpose, in the originator's words, "is not in predicting the future but in creating transformative spaces for the creation of alternative futures."
When to Use
- An issue is stuck because the framing is stuck: the litany and the system explanation have been argued to exhaustion and the disagreement is really about clashing worldviews and the unexamined story underneath.
- The goal is to open up genuinely different futures, not to optimize the current one.
- The question is contested, value-laden, long-horizon, civilizational, or cultural - the kind of issue where a deep metaphor ("growth is health," "the market knows best," "users are a passive funnel") is doing more work than any number in the litany.
- You suspect the official account is privileging one worldview and hiding others, and you want to surface whose framing this is and what it conceals.
When NOT to Use
- The problem is simple, technical, or single-cause. One event, one obvious cause, a known fix. Forcing a myth/metaphor layer onto a logistics bug manufactures false profundity; a method whose deepest layer is civilizational narrative is the wrong tool for "the deploy is failing." Say it is a simple cause and stop.
- You need a single-cause diagnosis and a leverage point. That is
think-iceberg-model: it descends four levels (event, pattern, structure, mental models) to find the structures and the mental models that cause a recurring problem, and pairs each level with an intervention. CLA refuses a single causal account on purpose and rebuilds upward into alternative futures instead. If you want one diagnosis and one fix, use the iceberg. - You need a forecast, a ranking, or a decision. CLA is explicitly not predictive and not an option-evaluation method, and it can induce analysis paralysis - too much problematizing, not enough deciding. Reach for it to reframe, then leave it for the decision tool.
- You want to model alternative external futures you do not control. That is
think-scenario-planning: 2x2 worlds built from critical uncertainties. CLA deconstructs the narrative and myth layer of one issue; it does not build a set of external worlds. - You want one fresh standpoint for the whole problem. That is
think-frame-creation: it abduces a single new frame. CLA rewrites four stacked layers at once and changes a civilizational myth, which a single reframe does not do. - You want to interrogate where the problem's boundary is drawn and who is left out. That is
think-boundary-critique. CLA can surface whose worldview is privileged, but its apparatus is the four-layer descent-and-rebuild, not a boundary judgment. - The reconstruction is skipped. Run only as a downward descent, CLA collapses into a four-box depth diagram and loses the one thing that distinguishes it - the up-the-layers rewrite into an alternative future. A descent with no reconstructed myth is just a heavier iceberg; do not ship it as CLA.
- The deconstruction is presented as objective truth. The worldview and myth readings are interpretive and contestable by design. Presenting "the real myth" as a discovered fact, rather than one reading among several, betrays the method and invites confident nonsense.
Instructions
When asked to reframe a stuck, contested, value-laden issue by reading and rebuilding the story underneath it, follow these steps:
- State the issue and confirm fit. Name the issue in one line. Confirm it is contested, value-laden, and long-horizon, and that the framing is what is stuck - not a simple technical problem. If it is single-cause or you need a decision or forecast, stop and route to the right tool (see When NOT to Use).
- Read the litany (current). Write the official, most-visible account: the headline numbers, the accepted problem statement, the "everyone knows" framing t