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-as-source-setup on a project that already has tessl init done and tessl-labs/spec-driven-development installed. The git repo is initialized but no enforcement scripts exist yet.",
"type": "weighted_checklist",
"checklist": [
{
"name": "creates-check-spec-links",
"description": "Creates scripts/check-spec-links.sh and makes it executable",
"max_score": 2
},
{
"name": "creates-check-target-ownership",
"description": "Creates scripts/check-target-ownership.sh and makes it executable",
"max_score": 2
},
{
"name": "creates-build-spec-manifest",
"description": "Creates scripts/build-spec-manifest.py",
"max_score": 1
},
{
"name": "creates-verify-sh",
"description": "Creates scripts/verify.sh and makes it executable",
"max_score": 1
},
{
"name": "creates-pre-commit-config",
"description": "Creates .pre-commit-config.yaml",
"max_score": 1
},
{
"name": "creates-ci-workflow",
"description": "Creates .github/workflows/spec-verification.yml",
"max_score": 1
},
{
"name": "asks-test-runner",
"description": "Asks the user which test runner the project uses before finalising the CI workflow",
"max_score": 2
},
{
"name": "shows-checklist",
"description": "Shows the post-setup checklist including pre-commit install and GitHub branch protection steps",
"max_score": 1
},
{
"name": "runs-spec-verify",
"description": "Runs spec-verify automatically at the end",
"max_score": 2
}
]
}