wv-guard-scope

To prevent scope drift during implementation, enforce task boundaries by validating work against established done_criteria and non_goals. This ensures new features adhere to existing codebase conventions and flags deviations before they cause pattern mismatches.

Enforcing code patterns during refactoring requires validating changes against existing conventions and task scope. Apply a guard mechanism during implementation to detect deviations and provide actionable guidance to correct mismatches or create new tasks.

Verify implementation scope by checking work against predefined done_criteria and non_goals. A guard validates alignment with these boundaries during execution, flagging feature creep or pattern drift to guide immediate corrective actions.

Create new tasks when scope drift is detected during implementation. If work deviates from established non_goals or introduces new code patterns, the guard flags these boundaries and provides actionable guidance to split the work into separate tasks.

Yes, a scope guard prevents feature creep by enforcing task boundaries during implementation. It validates work against current scope and existing conventions, flagging deviations to ensure implementation stays within established codebase patterns.

Refactoring introduces pattern mismatches when implementation deviates from existing codebase conventions. Without enforcing task boundaries and scope limits, changes drift from established patterns, requiring validation against non_goals to guide corrective actions.