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
#!/usr/bin/env bash
set -euo pipefail
echo "=== Spec Verification ==="
echo ""
bash scripts/check-spec-links.sh
bash scripts/check-target-ownership.sh
python3 scripts/build-spec-manifest.py
echo ""
echo "Spec checks passed. Running test suite..."
echo ""
if [ -f "pytest.ini" ] || [ -f "pyproject.toml" ] || [ -f "setup.cfg" ]; then
pytest tests/ -v
elif [ -f "package.json" ] && grep -q '"test"' package.json; then
npm test
elif [ -f "Cargo.toml" ]; then
cargo test
else
echo "No test runner detected. Run your test suite manually."
exit 1
fi