spec-verify

To verify code implementation against requirements and tasks, run an automated verification process that parses specification documents like requirements.md, tasks.md, and design.md. This checks if your code, tests, and documentation satisfy the defined specifications and generates a detailed status report.

Automated specification verification works by parsing your requirements.md, tasks.md, and design.md files to map defined tasks to actual code artifacts. It performs hybrid verification strategies to analyze code, tests, and documentation for requirement satisfaction, identifying any orphaned tasks or stale references.

Yes, you can check for orphaned tasks and stale references by running an automated coverage analysis against your specification documents. This process identifies any tasks left unimplemented or documentation references that are no longer valid, reporting them in a detailed verification report.

To run automated spec implementation completeness checks, you need to have your specification documents formatted as requirements.md, tasks.md, and design.md files within your current working directory. The verification tool will parse these files to map tasks to your code artifacts.

You should run a spec verification check after a developer completes a feature and before code is merged or deployed. This ensures that all user stories, requirements, and implementation tasks have been fully addressed in the code, tests, and documentation.

The best way to ensure requirements satisfaction before merging code is to automate the verification of software implementation against defined tasks and user stories. This reports on requirement coverage and highlights any unaddressed implementation tasks or orphaned code artifacts.