reducer

What problem does it solve? Systems accumulate branches, state, dependencies, layers, and moving parts over time, and naive simplification attempts often just relocate complexity or silently break behavior. This Skill provides a disciplined method to derive the minimum mechanism from first principles and prove that behavior and guarantees are conserved. ## Core Features & Use Cases - Behavior Conservation Ledger: Inventory every supported behavior, guarantee, and boundary with preservation evidence or explicit proof gaps before making changes. - Whole-System Complexity Baseline: Count control flow, state spaces, structure, and operational dimensions with consistent scope and method before and after reduction. - Reversible Slice Selection: Rank reduction candidates by mechanism removed, confidence, and blast radius, then implement the smallest reversible slice with behavior and mechanism gates. - Use Case: A service has grown to five layers of adapters, three feature flags, and duplicated retry policies. Use this Skill to baseline the mechanism, derive the minimum design, and remove one complete mechanism per slice while proving outputs, errors, and ordering stay identical. ## Quick Start Use the reducer skill to simplify this feature from first principles while preserving behavior and non-functional guarantees.