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
{
"context": "The agent is asked to run spec-verify. The project has specs/auth.spec.md with a requirement referencing [@test] ../tests/auth/test_login.py, but that file does not exist on disk.",
"type": "weighted_checklist",
"checklist": [
{
"name": "runs-check-spec-links-first",
"description": "Runs bash scripts/check-spec-links.sh as the first check",
"max_score": 1
},
{
"name": "reports-check-spec-links-failed",
"description": "Reports check-spec-links as FAILED",
"max_score": 2
},
{
"name": "identifies-spec-file",
"description": "Identifies specs/auth.spec.md as the spec containing the broken link",
"max_score": 2
},
{
"name": "identifies-missing-file",
"description": "Identifies tests/auth/test_login.py as the missing file",
"max_score": 2
},
{
"name": "explains-impact",
"description": "Explains that a missing [@test] means the requirement has no verifier",
"max_score": 1
},
{
"name": "no-premature-complete",
"description": "Does not declare implementation complete",
"max_score": 2
},
{
"name": "provides-fix-guidance",
"description": "Tells the user what to fix: create the missing test file or correct the [@test] path",
"max_score": 1
}
]
}