What problem does it solve?
This Skill helps you analyze tech debt, code rot, and maintenance risk by treating a codebase like a system that naturally drifts toward disorder unless active effort keeps it stable. It is especially useful when teams are tempted to ship now and defer cleanup, or when irreversible changes hide long-term costs.
Core Features & Use Cases
- Thermodynamic analysis of software decay: Reframes maintenance problems using entropy, free energy, reversibility, drift, and steady state.
- Refactor and migration decision support: Helps distinguish cheap-to-reverse code changes from one-way commitments like schema migrations, public APIs, and file formats.
- Maintenance budgeting: Surfaces who will actually pay for cleanup work, whether a forcing function exists, and where complexity is being exported rather than reduced.
- Use Case: Use this Skill when reviewing a legacy subsystem before a major migration to decide which disorder is acceptable, which drift is dangerous, and which irreversible changes need stronger safeguards.
Quick Start
Use the entropy-and-code-rot skill to evaluate whether a proposed shortcut creates reversible local mess or irreversible long-term maintenance cost.