vcx-scope-gate

To prevent scope creep, implement feature-scope governance by validating proposed work against documented manifests and ADR decisions before proceeding. This ensures only authorized, in-scope tasks advance through planning and review phases.

A feature-scope governance gate validates new features and scope changes against a feature manifest and ADR guidelines. It enforces authorization levels, cooldown periods, and required documentation before allowing development to proceed.

Validate a pull request by running a scope gate that checks PR artifacts against docs/sdd/FEATURE_MANIFEST.yaml and ADR decisions. The gate enforces 48h cooldowns and authorization levels to ensure only in-scope work proceeds.

Yes, you can enforce L-Lite, L-Std, and L-High authorization levels to control PR approvals for scope changes. The gate applies these levels to PRs and related artifacts to ensure proper governance.

Enforce a 48h cooldown period when a new feature or scope change is proposed during Phase 1. The governance gate triggers this cooldown alongside required ADR documentation checks to prevent rushed scope modifications.

Scope governance relies on existing ADR documentation and a feature manifest to validate alignment. Without these artifacts, the gate cannot verify if proposed work follows documented rules or authorized decisions.