principle-yagni

To identify over-engineering, you analyze feature necessity and scan for unused code, parameters, configurations, and excessive abstractions. This ensures you only implement currently required features, eliminating unnecessary complexity before it accumulates as technical debt.

The YAGNI principle dictates that you should only implement features currently needed, not predicted future ones. Apply it during code review to assess feature scope, detect over-design signals, and evaluate technical debt trade-offs across L1-L3 support levels.

Evaluating technical debt trade-offs involves weighing the cost of a simple implementation against the burden of an over-engineered solution. You analyze whether a new configuration is essential for current goals or a premature solution adding future maintenance cost.

Yes, you can run specific quick check commands to identify unused code, parameters, and excessive abstractions. This scans your project to confirm whether existing configurations and features are truly essential for your current requirements.

Yes, the approach evaluates technical debt trade-offs and feature necessity specifically across different support levels, labeled L1 through L3. It assesses whether your software design adheres to the YAGNI principle within the context of these varying support tiers.

You should not strictly apply the YAGNI principle when a feature is genuinely required for current operations rather than a future prediction. If the technical debt trade-off analysis confirms immediate need across L1-L3 support levels, implementing the full scope is necessary.