vibe-scope-gate

To prevent scope creep during feature kickoff, you can enforce scope compliance by validating proposed features against project boundaries and code budget constraints. This process checks new work alignment with declared policies and returns a structured pass, discuss, or reject decision.

Document-driven scope validation is the process of reading project identity files like SOUL.md and CLAUDE.md to determine if a proposed feature aligns with declared boundaries. It references explicit non-goals and core identity clauses to ensure new development avoids unnecessary implementation churn.

You can check if a new feature exceeds your code budget by retrieving the total budget from governance configuration files, estimating the lines of code impact for the proposed work, and comparing the estimate against the remaining budget to produce a deterministic pass or fail outcome.

Yes, you can use scope enforcement with existing CLAUDE.md and SOUL.md policies. The validation process directly reads these governance documents to reference specific clauses, checking proposed features against your project's core identity and explicit non-goals list to block conflicting work early.

The best way to automate scope compliance checks is to trigger validation automatically during new feature creation phases. This enforcement mechanism reads governance budgets, estimates code impact, and produces a structured report citing specific policy clauses with a clear recommendation to continue or reject.

Your proposed feature gets flagged by the scope gate because it conflicts with declared project boundaries in SOUL.md or CLAUDE.md, or its estimated lines of code impact exceeds the remaining budget allocated in your governance configuration. The report provides specific clause references for the rejection.