Menu

Individual skill

second-order-effects-analyzer

0upvotes

Analyzes downstream cascade effects, systemic feedback loops, and unintended consequences of technical decisions.

skills/reasoning/second-order-effects-analyzer/SKILL.md

Read pinned source

Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
27
Repository last updated
Aug 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Purpose

Anticipate the multi-order ripple effects ("and then what?") of architectural changes, API deprecations, schema updates, or rate limit adjustments across interrelated systems, teams, and user habits.

## When to Use

- Proposing a breaking change or deprecation.
- Adding strict rate limits, database indexes, or caching layers.
- Changing pricing tiers, billing models, or developer API quotas.

## What to Analyze

1. **First-Order Effect (Immediate Intent)**: What does this change directly accomplish?
2. **Second-Order Effects (Downstream Systems)**: How do upstream callers, batch jobs, and databases react?
Back to top