avoid-scope-creep

To prevent scope creep during code refactoring and bugfixing, enforce changes strictly as requested by rejecting any unsolicited modifications like extra features or style cleanup. Only change what was explicitly asked.

Scope creep in software engineering change management is doing unrequested work such as adding extra features or cleaning up style when a specific targeted change was needed. It happens when changes deviate from the explicit request.

To keep code reviews aligned with the original request, apply guardrails that reject unsolicited modifications and ensure changes strictly adhere to the defined scope. Only approved modifications should pass the review.

Yes, you can use spec adhesion rules for targeted bugfix workflows. Spec adhesion ensures changes are bounded to the explicit request, preventing unnecessary modifications and keeping the bugfix strictly aligned with the product scope.

You should avoid introducing unrequested work in development processes when product or design dictates the scope and changes must be bounded. Only change what was explicitly asked to maintain strict spec adherence.