validate-checkpoint

The mechanism works by coordinating script execution across all workflow stages like PRD, Discovery, and SPECs, then collecting results into structured JSON reports with pass/fail statuses and exit codes to enforce guardrails.

Enforcing workflow guardrails is achieved by validating checkpoint readiness across all stages, yielding actionable warnings and exit codes that prevent progression when artifacts are incomplete or unlinked within the docs-first workflow.

Yes, checkpoint validation generates structured JSON reports containing collected results and clear pass/fail statuses. These reports provide actionable warnings and exit codes to directly drive automated gating decisions for the next workflow stage.

You validate ADRs and OP-NOTES readiness by invoking the validator to check artifact completeness, linkage, and criteria compliance across the project. It orchestrates these checks to verify overall checkpoint readiness before stage progression.

Yes, you can use checkpoint validation across all VibeFlow docs-first stages including PRD, DISCOVERY, SPECs, ADRs, and OP-NOTES. The validator applies uniformly to ensure artifacts meet defined criteria before passing stage gates.