specd-verify

To verify code changes against spec scenarios, load the change state, apply deltas, and validate results against the merged spec scenarios. This structured workflow ensures your implementation meets all required criteria before progressing toward archiving.

Preventing drift between design specs and implementation requires a graph-guided workflow with mandatory context loading and guardrails. Merging specs with deltas and validating scenarios enforces reproducible verification and reduces drift between design and implementation.

Pre and post hooks execute during the change verification lifecycle to ensure reproducible, guarded deployments. They integrate with context loading to validate results and enforce strict workflow transitions when verification failures occur.

Artifact reviews and signoff gates guide users through recommended transitions during change verification. They validate merged spec scenarios, enforce guardrails, and direct the workflow toward archivable states only when all verification criteria pass.

Loading change state to start the verification workflow requires running the change status command with the target name. This loads the current state, applies deltas, and validates scenarios against required requirements to ensure reproducible verification.