second-order-thinkinglisted

# Second-Order Thinking ## Overview First-level thinking asks "what will happen?" and stops. Second-order thinking asks "...and then what? and then what?" — tracing the chain of consequences past the immediate effect to the ones that aren't obvious, especially the ones that **reverse** the first effect once other people and the system respond. This is the third motion in the collection, distinct from its neighbors: [first-principles](../first-principles/SKILL.md) decomposes *downward* to bedrock; [occams-razor](../occams-razor/SKILL.md) chooses *sideways* among competing explanations; second-order thinking traces *forward* through time and consequence. They compose — reduce to find the foundations, choose the simplest explanation that fits, then trace where the decision actually leads. ## When to Use Apply when: immediate effect is obvious but downstream effects are not; "everyone agrees" (is it priced in?); other actors will respond or feedback loops exist; someone asks "and then what?" / "what are the second-order effects?" / "what could go wrong downstream?" **When NOT to use:** genuinely low-stakes reversible decisions; you lack a causal model (build it first); the chain would be pure speculation with no grounding. ## Coaching Novices (Adaptive Front Door) Before running the Process, read the user. This skill has two delivery modes — pick one, don't default to dumping a finished cascade. - **Engine mode (do-it-for-me):** the user brought a concrete decision and w