speckit-verify-run

To verify code implementation against project specifications, you cross-reference spec.md, plan.md, tasks.md, and constitution.md against the codebase to detect alignment gaps early. This produces a risk-scored verification report with actionable remediation guidance without modifying existing code.

Cross-artifact verification is the process of checking spec.md, plan.md, tasks.md, and constitution.md for consistency against implemented features. It guarantees traceability between tasks, reviewed files, and requirements while enforcing constitution-driven decisions before merging branches.

To generate a verification report for Spec-Kit feature branches, execute the verification step after completing the implementation phase. It analyzes the .specify/memory constitution artifacts and outputs a compact report containing findings, risk levels, and recommended actions.

Post-implementation verification does not modify source code during the audit. It acts as a read-only guardrail that analyzes specification artifacts and the implemented codebase to catch gaps early and enforce compliance before deployment.

Automated spec verification is designed for pre-merge compliance checks. It validates feature-branch implementations against the project constitution and specification artifacts to ensure traceability and catch requirement gaps before release.

Release guardrails using specification artifacts are limited to projects with a .specify/memory constitution and existing spec.md, plan.md, tasks.md, and constitution.md files. The verification process detects gaps and reports risks but does not automatically fix the implementation code.