gsd-validate-phase

To validate plans in a project phase, load the phase file and enumerate each plan to check its execution, verification, documentation, and commit status. This process ensures end-to-end quality gates are passed before proceeding to the next phase.

Phase validation in a phase-based workflow is a quality gate mechanism that verifies every plan within a phase has been executed, verified, documented, and committed. It prevents pipeline failures by generating a consolidated validation report before progression.

Check phase completion status by loading the phase file to run gate validations on all enumerated plans. The validation confirms executed, verified, documented, and committed statuses, emitting a concise actionable report for stakeholders.

Yes, phase validation works directly with GSD Hermes planning files. It loads phase files like .planning/phases/phase-N.md to enumerate plans and validate their execution, verification, documentation, and commit statuses.

Phase progression fails when plans lack documentation because validation enforces strict quality gates. The validation process checks that all plans have executed, verified, documented, and committed statuses to prevent gaps before moving to the next phase.

Yes, you can automatically generate a validation report for phase plans. The validation process loads the phase file, enumerates all plans, runs gate validations, and emits a consolidated report detailing execution, verification, documentation, and commit statuses.