Adds spec-as-source enforcement to any project using spec-driven development
87
91%
Does it follow best practices?
Impact
82%
2.34xAverage score across 5 eval scenarios
Passed
No known issues
Run spec-verify on this project.
Project state:
scripts/check-spec-links.sh exists and is executable
scripts/check-target-ownership.sh exists and is executable
scripts/build-spec-manifest.py exists
specs/auth.spec.md exists and contains this requirement:
Users must be rate-limited by IP. [@test] ../tests/auth/test_login.py
tests/auth/test_login.py does NOT exist on disk
The project uses pytest (pytest.ini is present)
Expected behaviour: check-spec-links must fail and report the missing file. Do not proceed to mark implementation as complete. Explain what needs to be fixed.