gsd-validate-phase

Use the validate-phase workflow to audit completed phase execution and reconstruct VALIDATION.md and SUMMARY.md files, ensuring all documentation accurately reflects the generated artifacts while preserving existing workflow gates.

Retroactive validation gap filling audits a completed phase to identify missing test coverage, then generates the necessary test files and updates VALIDATION.md to restore documentation integrity and prevent regressions.

Run the validate-phase workflow to compare completed phase artifacts against existing documentation, automatically generating missing test files and updating VALIDATION.md to align records with the actual executed work.

Yes, the validate-phase workflow retroactively reconstructs and validates SUMMARY.md and VALIDATION.md while strictly preserving all existing workflow gates, ensuring no phase progression rules are bypassed during the documentation update.

Run a phase validation audit immediately after a phase has completed execution but before moving to the next stage, allowing you to detect coverage gaps and retroactively fill them before they cause downstream regressions.

The best way to close Nyquist validation gaps is to audit the completed phase artifacts, validate the existing documentation, and retroactively generate tests to fill any identified coverage holes while maintaining workflow gate integrity.