What problem does it solve?
Software systems accumulate branches, states, flags, layers, and operational machinery that increase maintenance cost. This Skill provides a disciplined workflow to remove that mechanism while proving that observable behavior and non-functional guarantees are preserved, rather than merely relocated or hidden.
Core Features & Use Cases
- Behavior Conservation Ledger: Classifies documented contracts, relied-upon behavior, disputed bugs, and obsolete internals, then tracks preservation evidence and fidelity gaps for each.
- Whole-Mechanism Accounting: Baselines control flow, state and time, structure, and operational variability across the full path, then recounts the same dimensions after the change to prove net removal.
- Gated Reduction Slices: Separates behavior and mechanism gates, distinguishing reduction transitions from terminal reductions so partial progress never claims a finished reduction.
- Use Case: A service has three retry layers, two feature flags, and a legacy adapter chain. Use this Skill to diagnose the minimum mechanism justified by real constraints, then execute an authorized slice that deletes the superseded machinery with evidence.
Quick Start
Use the reduce-system-complexity skill to diagnose the checkout payment path and propose a reduction that removes the legacy retry and flag machinery while preserving its documented behavior.
