sdd-verify

Spec-fit verification checks a completed change against the accepted spec and plan to identify CRITICAL, WARNING, and SUGGESTION findings. It acts as a final verification gate before PR submission, ensuring delivery matches documented success criteria and constraints.

Auditing changes against a project plan involves a multi-axis spec-fit check that produces a formal verdict of APPROVE or REQUEST CHANGES. Findings are recorded in tasks.md with citations to exact files and lines where criteria are satisfied or violated, creating an audit trail.

To verify changes match risk criteria, run the verification workflow after applying changes and before opening a PR. The process evaluates alignment with documented goals, constraints, and risks, generating a formal verdict and recording findings for audit purposes.

Spec-fit verification is needed after sdd-apply is complete and the change is ready for PR review. It serves as the final gate before opening a PR, ensuring the implementation conforms to the accepted spec, plan, and documented success criteria.

Yes, the verification process generates a formal verdict of APPROVE or REQUEST CHANGES based on a multi-axis check against the approved spec and plan. It identifies findings categorized as CRITICAL, WARNING, or SUGGESTION to guide PR preparation.

Yes, spec-fit verification records all findings in tasks.md for audit purposes, including citations to exact files and lines where criteria are satisfied or violated. This creates a formal audit trail supporting quality assurance and lifecycle compliance.