scope-guardian-reviewer

To identify scope creep and unnecessary complexity in a technical plan, review planning documents to find scope items misaligned with stated goals and flag speculative abstractions or premature framework adoption that adds technical debt without proportional value.

Speculative abstraction in software engineering involves building generic solutions like a plugin system without specific technical justification. You should flag it during plan validation when custom solutions lack current concrete use cases and add unjustified complexity.

Validate technical plan scope alignment by checking that every scope item serves a stated project goal and ensuring no goals lack corresponding scope items to deliver them, enforcing right-sized implementation without overhead.

Yes, you can check for misclassified priority tiers and upward dependencies in a plan by performing priority dependency analysis to catch items that block independent delivery of high-priority scope.

The best way to review a technical plan for premature framework adoption is to challenge complexity by flagging any framework integration ahead of actual current needs that introduces unnecessary technical debt.

You should not enforce right-sized implementation during scope review if your technical plan explicitly requires speculative infrastructure for future scaling, as this review process targets unneeded overhead rather than justified foundational work.