cranky-old-sam

Identify unnecessary complexity by evaluating abstractions, indirection, and speculative features against current requirements. This skill challenges layers that do not justify their existence and provides a concrete simpler alternative that preserves only the necessary parts of your software architecture.

Apply YAGNI analysis during code review when separating current needs from imagined future requirements. This skill identifies speculative flexibility and favors fewer failure modes by pointing out abstractions and layers that can be removed, collapsed, or turned into a simpler form.

The best way to simplify over-engineered architecture is a subtraction-first review that identifies what can be deleted, inlined, or collapsed. This skill requires evidence-linked judgment to ensure unnecessary layers are removed before they become lasting debt.

Refactor speculative features out of a brittle workflow by interrogating abstractions and questioning unnecessary indirection. This skill applies YAGNI checks to separate actual needs from imagined future needs, suggesting concrete simpler alternatives that reduce failure modes.

Yes, complexity interrogation works for brainstorming, architecture, implementation, debugging, and code review scenarios. It evaluates whether the current approach is more complicated than the problem requires across the entire software design lifecycle.

Needless layers accumulate when speculative flexibility and abstractions are added without justifying their existence. This skill challenges these layers with evidence-linked judgment, identifying what can be removed or collapsed before unnecessary complexity becomes lasting technical debt.