structured-analysislisted

# Structured Analysis Eight analytic frames for reasoning about a topic's **background** (how it came to be) and **future** (where it might go). Each frame is a discipline, not a template. The skill's job is to pick the right frame for the question, run it to depth, and refuse to produce shallow bullet-list output. ## Core principle Most analysis fails in one of three ways: it stays on the surface (bullets without causal chain), it hides its assumptions (confident forecast built on unexamined ground), or it treats one perspective as objective (blind to how the other side reads the same facts). The eight frames each attack one of those failure modes. Use them singly or in combination — never all at once. ## Decision flow — how to pick frames Follow this order every time. Do not skip step 3. **1. Explicit override.** If the user names a frame, a count, or a direction, obey it and skip to step 3. - Frame named: *"run a red team on this"*, *"do a genealogy"* - Count: *"one frame only"*, *"two angles"*, *"go deep with three"* - Direction: *"just the background"* → backward-looking frames only (1–5) / *"just the future"* → forward-looking frames only (6–8) **2. Trigger phrase in the user's message.** Check the trigger dictionary at the bottom of this file. If one or more phrases match, select those frames. **3. No signal → default match.** Read the topic, match it to the topic-type table below, pick the paired frames. **4. State the selection and invite additions. Then wai