[Proposal] /opsx:validate command to check code against the living specs #880
Description
The OpenSpec codebase currently has /opsx:verify command that can be used to check implementation against change artifacts (the ones in openspec/changes/<name>/).
However, there's no equivalent for validating the current implementation against the main specs in openspec/specs/. This seems like a gap; why keep 'source of truth' specs when the toolset doesn't provide tools to make direct use of them?
As an example. The 'Contributing' section of the 'README.md' in this repo says for example "Small fixes — Bug fixes, typo corrections, and minor improvements can be submitted directly as PRs." - it seems probable that in any project there will be small changes and adjustments where raising an openspec change is overkill. In that case it would be the living spec where any change could be directly documented (would be on the developers then to decide how or if they want to document the deviation from the archived changes)
This suggestion is for a command like /opsx:validate <spec-name> so users would have both tools:
/opsx:verifyfor checking changes/opxs:validatefor checking current specs
Given that the main spec does not have design or tasks, this command would check correctness only, not completeness or coherence, so would be a less detailed report than/opsx:verify.