Spot architectural debt and refactoring wins

Reads your codebase, architecture-decision records, and domain language docs, then surfaces tightly-coupled modules, testability gaps, and consolidation opportunities with a priority order.

Best for: Engineering leads planning the next refactor or sprint—need ammunition to justify cleanup work.

Engineering / planning-thinkingatomicfor-engineersneeds-integrationfrom-repo

Source

Creator's repository · mattpocock/skills

View on GitHub

License: MIT