scope-guard

A scope contract prevents scope creep by defining allowed actions, excluded actions, target files, and done-criteria before coding begins. It gates implementation progress until the contract is formally approved, ensuring only authorized work proceeds.

To create a scope contract, list allowed actions, files, and done-criteria, then validate against Context7 before implementation. This generates a formal whitelist specifying what to do, what not to do, and target files to curb over-engineering.

A whitelist contract is a formal scope agreement detailing what to do, what not to do, target files, and done-criteria before coding begins. It prevents over-engineering by gating progress until the explicit scope guidance is approved.

Yes, Context7 integration works for validating done-criteria against official documentation. The scope validation process checks your defined completion criteria using Context7 to ensure implementation requirements align with official library docs.

You need a formal scope contract for a code refactor when over-engineering risks exist and explicit guidance is required. It enforces a whitelist of allowed files and actions, preventing scope creep before any substantive work begins.