Anti Entropy Governance

When you're cleaning up legacy code and need to decide whether to delete old paths, keep compatibility shims, or stop for explicit approval, this skill enforces a clear hierarchy: internal code gets deleted first by default, proven external dependencies get compatibility exceptions only with evidence, and anything touching persistent state or irreversible data requires scoped user confirmation before execution. It's designed to be composed by other skills like brainstorming or writing-plans rather than called directly. The core tension it resolves is whether your next move should reduce entropy by removing dead code or whether you're about to accidentally break a real dependency or destroy live data. Think of it as a deletion safety referee that knows the difference between retiring a stale fallback branch and dropping a production database table.