speckit-verify-run

Spec compliance verification checks your codebase against spec.md, plan.md, tasks.md, and constitution.md in a read-only workflow. It analyzes task completion, file existence, requirement coverage, and scenario gaps, then outputs a structured Markdown report with severity-assigned findings.

Constitution MUST enforcement flags critical conflicts with non-negotiable principles defined in constitution.md as CRITICAL findings during spec compliance checks. This prevents integration drift by ensuring implementation changes respect foundational constraints before moving forward.

Run a non-destructive verification workflow that detects missing implementation evidence for requirements, incomplete tasks, and unresolvable referenced files. It produces a compact Markdown report showing whether your implementation aligns with the specification artifacts.

Yes, spec verification runs with no extra arguments and has no external dependencies. It requires only the presence of spec.md, plan.md, tasks.md, and constitution.md artifacts in your project to perform evidence-driven coverage checks and output findings.

Spec compliance verification respects a configured max_findings limit to cap the number of reported issues. This read-only audit assigns severity levels to each finding, allowing you to prioritize CRITICAL constitution conflicts and coverage gaps without being overwhelmed.

Verification reports show scenario coverage gaps when tests fail to cover scenarios defined in your specification artifacts. The non-destructive audit detects these gaps alongside missing requirement evidence and incomplete tasks, assigning severity to each finding for prioritized resolution.