reducing-entropy

Reduce technical debt by applying a deletion-first mindset that defaults to removing code rather than adding new functionality, measuring success by the final code quantity rather than effort expended during refactoring.

Minimize code size by loading reference mindsets to guide deliberate deletion and simplification decisions, actively flagging common anti-patterns and excuses for code growth during legacy module cleanup.

A deletion bias mindset works for feature scoping by evaluating reductions and defaulting to code removal, ensuring the end-state metric reflects a smaller total codebase instead of added complexity.

Yes, you must load one or more mindsets from references before evaluating codebase reductions, as this manual-only skill relies on explicit user activation and reference mindsets to guide simplification decisions.

Avoid a delete-first approach when explicit user activation is absent or reference mindsets cannot be loaded, as the framework requires deliberate simplification decisions rather than automated code removal.

Yes, you can use this framework to identify common excuses for codebase growth and flag them as anti-patterns, applying a deliberate deletion bias to counteract unnecessary code accumulation during refactoring.