gsd-verify-work

To verify plan steps, you execute verification criteria from a PLAN.md file and generate a VERIFICATION.md report. This process systematically validates phase completion and records traceable evidence with a final PASSED or FAILED status.

Automating phase gate verification involves reading defined acceptance criteria from PLAN.md and auto-generating a VERIFICATION.md file. This yields deterministic phase results and traceable evidence, ensuring formal validation before advancing stages.

Creating a traceable verification report requires executing planned validation steps and recording the evidence in VERIFICATION.md. The generated document contains a table of step results and a final PASSED or FAILED indicator for full traceability.

Yes, you need a repository containing a PLAN.md file within a .planning directory. The verification process reads this specific markdown format to execute steps and output the corresponding VERIFICATION.md document.

Yes, this verification approach is specifically designed for software development workflows requiring formal phase completion. It executes planned steps, collects evidence, and outputs a status report to satisfy deterministic phase gate requirements.

A FAILED status in your verification report indicates that one or more acceptance criteria defined in PLAN.md were not met during execution. The generated VERIFICATION.md provides a table detailing which specific step results caused the failure.