scope-completeness-validator

Scope completeness validation is a checklist-based gate that prevents gaps from derailing PERT estimates by ensuring all required scope categories are explicitly addressed. It leverages existing scope context from staged proposals and memory to ground coverage decisions before sizing begins.

The best way to identify missing scope categories like integration testing and data migration is to apply a formal validation gate against existing scope context. This surfaces missing areas and produces a formal Scope Completeness Report for final decision.

You generate a scope completeness report for project governance by running a validation gate after scope establishment and before sizing. It assesses categories like RBAC and NFRs, outputting a formal report with per-category statuses for final decision.

Scope validation belongs in an estimation-sizing-thinking workflow after the Scope Establishment phase and before PERT sizing. Running it at this gate ensures missing categories are surfaced before effort sizing can be derailed by coverage gaps.

Yes, you can use staged proposals and claude-memory to ground scope coverage decisions by extracting existing scope descriptions from them. This context allows the validation gate to accurately determine if required categories are Present, Explicitly Excluded, or Missing.

Scope areas that should be checked to prevent gaps in effort sizing include integration testing, RBAC, NFRs, external dependencies, data migration, and environment coverage. A validation gate assesses these areas to produce a formal completeness report.