speckit.validate

To validate code against specification requirements, run a post-implementation review that compares source files with spec.md to identify mismatches, check acceptance criteria, and generate a traceability matrix mapping requirements to implementation.

Generating a requirements traceability matrix involves extracting functional requirements and edge cases from spec.md, then mapping them to the code and files referenced in tasks.md to verify implementation coverage and produce a validation report.

Checking test coverage and edge-case handling requires analyzing implementation files against specification documents to verify requirement coverage, test presence, and generate an actionable validation report with pass, partial, or fail status.

Automated post-implementation validation requires spec.md, plan.md, and tasks.md to be available, along with accessible source files created or modified by the implementation, ensuring accurate requirement mapping and coverage analysis.

Automated code review identifies unhandled edge cases and missing acceptance criteria by comparing project artifacts and code against formal specification documents, flagging gaps, and writing prioritized remediation recommendations to validation-report.md.

Post-implementation validation sets an exit status based on coverage thresholds to programmatically signal whether the implementation meets the required specification coverage, enabling automated CI/CD pipeline gates and immediate remediation alerts.