speckit-verify

To verify implementation against a spec without modifying files, use a non-destructive post-implementation gate. It loads artifacts like spec.md and tasks.md to perform read-only alignment checks and outputs a structured Markdown verification report.

Evidence-based spec alignment traces functional requirements to implementation evidence found in files referenced by completed tasks. It validates requirement coverage, scenario coverage, and constitution MUSTs deterministically for repository QA.

To check task completion and constitution guardrails after implementation, run a verification gate. It builds task inventories, validates completed tasks against plan.md, and checks alignment with constitution MUSTs.

Yes, the verification process caps token usage by generating deterministic, token-efficient outputs. It limits findings to a maximum of 50 items and produces a structured Markdown report with recommended next actions.

Yes, you can validate functional requirements using spec.md and plan.md artifacts. A read-only verification gate loads these files to check requirement coverage, scenario coverage, and alignment without altering the repository.