scope-guard

Prevents overengineering through worthiness scoring, opportunity cost comparison,and branch threshold monitoring.Triggers: scope creep, overengineering, worthiness score, branch size, YAGNI,feature evaluation, scope validation, anti-overengineering, opportunity costUse when: evaluating features during brainstorming, planning new functionality,branches approach size limits (1000/1500/2000 lines, 15/25/30 commits)DO NOT use when: feature is already approved and in progress.DO NOT use when: simple bug fixes with clear scope.Use this skill BEFORE implementing any new feature. This is NON-NEGOTIABLEfor scope control.