second-order

Analyzes proposed actions to generate first-, second-, and third-order consequence chains.

1|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/bcbeidel/toolkit --skill second-order-bcbeidel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: second-order
Source: https://github.com/bcbeidel/toolkit/tree/main/plugins/consider/skills/second-order
Command: npx skills add https://github.com/bcbeidel/toolkit --skill second-order-bcbeidel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Trace the consequences of actions beyond the obvious, identifying second- and third-order effects before they occur.

Core Features & Use Cases

  • Structured guidance to capture a proposed action, enumerate first-order effects, and iteratively extend the chain to second- and third-order outcomes.
  • Detect feedback loops and map unintended consequences to reveal systemic risks and opportunities in policy planning, product strategy, and operations.
  • Reassess decisions with a complete visibility of consequence chains to support more informed governance.

Quick Start

Provide a proposed action or decision to evaluate and let the tool generate the full consequence chain.

Frequently Asked Questions about second-order

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I trace second- and third-order consequences of a decision?

To trace second-order consequences, provide a proposed action to generate a structured chain extending from first-order effects to downstream third-order outcomes, identifying feedback loops and unintended consequences.

What is second-order consequence analysis in systems thinking?

Second-order consequence analysis is a systems-thinking method that evaluates proposed actions to reveal downstream impacts beyond immediate effects, mapping feedback loops and unintended consequences to support informed decision-making.

How do I identify unintended consequences and feedback loops in policy planning?

You identify unintended consequences by iteratively extending a proposed action's first-order effects into second- and third-order outcome chains, which reveals systemic risks and feedback loops relevant to policy planning.

Can I use consequence analysis for product strategy and operations decisions?

Yes, consequence analysis applies across scenarios like product strategy and operations to map systemic risks and opportunities by revealing downstream impacts that are not yet understood from immediate first-order effects.

What is the best way to map downstream impacts of a proposed action?

The best way to map downstream impacts is to capture the proposed action, enumerate its first-order effects, and iteratively extend the chain to generate second- and third-order outcomes with identified feedback loops.

When do I need second-order consequence analysis for scenario planning?

You need second-order consequence analysis when immediate effects of a proposed action exist but downstream impacts are not yet understood, requiring a structured chain of effects to support scenario planning.