vibe-ai/spec-as-source
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
Evaluation results
100%
86%Use spec-rebuild to prove that specs are the source of truth. The project has specs/auth.spec.md with targets: src/auth.py and tests/test_auth.py. The working tree is clean (no uncommitted changes).
safety-check-uncommitted
0%
100%
safety-check-specs-exist
0%
100%
shows-deletion-list
0%
100%
asks-confirmation
0%
100%
no-delete-infra
100%
100%
generated-header
0%
100%
test-annotations
0%
100%
runs-spec-verify
0%
100%
reports-success
0%
100%
53%
-31%Use spec-ci-sync to update the CI workflow for this project.
detects-pytest
100%
100%
reads-manifest
100%
0%
identifies-test-files
100%
0%
generates-pytest-workflow
100%
100%
includes-test-files-in-cmd
100%
0%
includes-spec-checks
0%
100%
shows-diff-and-confirms
100%
0%
no-extra-runners
100%
100%
100%
100%Run spec-verify on this project.
runs-check-spec-links
0%
100%
runs-check-target-ownership
0%
100%
runs-build-spec-manifest
0%
100%
runs-test-suite
0%
100%
reports-summary-table
0%
100%
reports-overall-passed
0%
100%
no-skip-on-pass
0%
100%
61%
Use spec-as-source-setup to add spec-as-source enforcement to this project.
creates-check-spec-links
50%
50%
creates-check-target-ownership
50%
50%
creates-build-spec-manifest
100%
100%
creates-verify-sh
0%
0%
creates-pre-commit-config
100%
100%
creates-ci-workflow
100%
100%
asks-test-runner
50%
0%
shows-checklist
0%
100%
runs-spec-verify
100%
100%
100%
82%Run spec-verify on this project.
runs-check-spec-links-first
0%
100%
reports-check-spec-links-failed
0%
100%
identifies-spec-file
0%
100%
identifies-missing-file
0%
100%
explains-impact
0%
100%
no-premature-complete
100%
100%
provides-fix-guidance
0%
100%
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6
Table of Contents