Complexity Check

You just made changes. Before you ship them, run four independent lenses on the diff. Each asks a different question:

1. Additions — was each new thing necessary?
2. Premises — could any assumption be dropped to delete code?
3. Spread — is the concept localized?
4. Duplicates — does something like this already exist?

The lenses are independent — findings from one rarely overlap with findings from another. Apply only the lenses that have signal to find for your diff; mark the rest N/A in the output with a one-line reason, so the reader can see the lens was considered.

When to run this

• After implementing a feature or bug fix, before committing
• After a refactor that touched more files than expected
• When something felt harder to write than it should have been
• When you were tempted to add "for future flexibility"

Skip the whole skill for: tiny fixes (typos, renames, dep bumps), pure deletions, mechanical refactors.