workflow-kit-verify

You can verify implementation changes against spec by checking spec coverage, task completion, scope boundaries, and test evidence against workspace artifacts. The process reads spec.md, plan.md, scope.md, and tasks.md, then updates verification.md with status, gaps, risks, and a readiness decision.

Change validation prevents scope creep by enforcing scope.md boundaries to verify changed files comply with freely editable, confirmation, or forbidden rules. It detects drift by confirming implementation matches spec and plan, then flags stale docs or unplanned scope creep instead of silently rewriting requirements.

Evidence-driven verification runs checks prioritized by verification.md and records automated or manual test results. It requires reading all relevant workspace artifacts, running allowable checks where possible, and documenting evidence, gaps, risks, and the final readiness decision in verification.md.

Yes, completeness checks against spec ensure all P0 mandatory acceptance criteria and required tasks are actually satisfied or explicitly marked as not done. The process records manual results, gaps, and risks in verification.md when automated checks are unavailable or cannot be run.

Spec verification should not be used when workspace artifacts like spec.md, plan.md, scope.md, tasks.md, and verification.md are missing or incomplete. It requires reading these workspace contract files to define completion gates and cannot validate changes or produce a readiness decision without them.