What problem does it solve? Software designs, plans, and implementations often accumulate machinery beyond what the current need requires. This Skill provides a read-only assessment that identifies overengineering and recommends the smallest safe alternative, so teams avoid building and maintaining complexity nobody asked for. ## Core Features & Use Cases - Necessity testing: Compares each boundary, responsibility, and data path against actual consumers and protected constraints using a remove-reuse-native-build ladder. - Independent review: Dispatches a subagent reviewer that has not authored the subject, returning a single structured readout without editing files. - Decision framing: Builds a fixed frame from the user's stated goals, hard constraints, and behaviors that must be preserved, treating unverified additions as proposals. - Use Case: Before implementing a plan that introduces a new caching layer and message queue, run this Skill to check whether reusing an existing mechanism or a native platform capability satisfies the stated need with less machinery. ## Quick Start Ask the agent to check whether the proposed architecture for the notification service can be simplified against the current requirements.
