phase-gate

Automated phase-gate validation enforces completeness by checking requirements, design, test, and code artefacts in docs/specs/<feature-id>, blocking progression when items are missing or cross-phase references are broken.

Cross-phase reference validation is the process of verifying that links between requirements, design, test, and code artefacts remain intact across the SDLC. It ensures that each phase's output correctly references and aligns with the preceding phase's artefacts.

You can block feature progression by applying a phase-gate validator to the feature's artefact directory. The validator checks for the existence of requirements, design, test, and code documents and halts progression if required artefacts are not found.

Yes, phase-gate validation operates directly on docs/specs/<feature-id> directories to locate and validate feature artefacts. It uses Python validators to check the existence and cross-phase reference integrity of the files stored there.

Feature progression is blocked when cross-phase references are broken because the validators detect integrity gaps between requirements, design, test, and code artefacts, reporting specific reference errors to guide remediation.

Automated phase-gate validation is limited to checking artefact existence and cross-phase reference integrity within the specified directory. It does not validate the qualitative content of the artefacts themselves, only their structural presence and linkage.