speckit-verify-run

To verify implementation against acceptance criteria read-only, you can validate the codebase against spec.md, plan.md, tasks.md, and constitution.md to confirm requirement and scenario alignment without altering files.

Post-implementation specification verification is a non-destructive quality gate that checks finished work against agreed artifacts. You need it to prevent broken implementations before code changes proceed further in the pipeline.

To check tasks coverage and confirm referenced files exist, perform an implementation audit that validates task completion, verifies files on disk, and reports evidence using token-efficient deterministic verification reports.

Yes, read-only validation enforces constitution compliance by applying MUST principles during the verification process, ensuring the current implementation strictly adheres to the rules defined in constitution.md.

Yes, you can validate spec scenarios and test alignment by checking the current implementation against the defined scenarios and acceptance criteria present in the specification artifacts to ensure codebase alignment.

A deterministic verification report provides token-efficient evidence reporting for implementation audits, but is limited to strict read-only execution, meaning it cannot automatically fix broken implementations or modify any project files.