Second-Order Consequences

Second-Order Consequences is an AI Engineering skill for Claude Code, published by tjboudreaux in cc-thinking-skills.

969 stars133 forkson tjboudreaux/cc-thinking-skillsAdded 2026/08/21+1% in starsRepository updated 2026/08/07

agent-skillsai-toolsanthropicclaudeclaude-codecritical-thinkingdecision-makingfirst-principlesmental-modelsproblem-solvingsystems-thinking

Install in seconds

Install Second-Order Consequences

Copy Second-Order Consequences into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/tjboudreaux/cc-thinking-skills/tree/main/skills/thinking-second-order ~/.claude/skills/thinking-second-order

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/tjboudreaux/cc-thinking-skills.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: skills/thinking-second-order/SKILL.md in tjboudreaux/cc-thinking-skills
Installs to: ~/.claude/skills/thinking-second-order
Collection: One of 25 skills cataloged from this repository
Category: AI Engineering — 2451 skills

What Second-Order Consequences does

Second-Order Consequences traces immediate and delayed effects of a change across actors, incentives, and scale before you commit. Use it for strategy, policy, architecture, or any choice where the obvious fix may backfire later.

Second-Order Consequences is cataloged under AI Engineering on DirSkills. Second-Order Consequences comes from a repository tagged agent-skills, ai-tools, anthropic, claude and claude-code.

Documentation

README

Excerpt

Second-Order Consequence Chains

Do not stop at the intended first effect. Trace what happens next across actors, time, and feedback until the chain stops changing the decision.

When to Use

Strategic, policy, incentive, or architecture choices with lasting coupling.
The obvious fix feels too easy or has known backfire patterns.
Success or scale would create new problems (load, gaming, debt).
Need to compare options by delayed effects, not only day-one benefit.

When NOT to Use

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Second-Order Consequences

What else does tjboudreaux publish alongside Second-Order Consequences?
Second-Order Consequences is one of 25 skills that DirSkills catalogs from tjboudreaux/cc-thinking-skills, the repository it ships in. Its siblings there include Bounded Rationality, Circle Of Competence and Effectuation. Each one is a separate skill with its own page in this directory, installs the same way Second-Order Consequences does, and is maintained by tjboudreaux in that same repository. The rest of the collection is listed on the tjboudreaux/cc-thinking-skills page.
How does Second-Order Consequences compare to other AI Engineering skills?
Second-Order Consequences ranks #1405 by stars among the 2451 AI Engineering skills in this catalog. The most-starred ones next to it are Architecture Decision Records, AI-First Engineering and Agentic OS. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Second-Order Consequences against them. Open each page to compare what they document and how they install.