verify-spec
Skill2 starsChanged 7 months agoMITView on GitHub
Extract acceptance criteria from a spec, classify each item, run automatic checks where possible, and return a structured verification report.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- mazzsva/claude-skillstheir own version, first seen Nov 16, 2026
- fclabs/skillstheir own version, first seen Oct 16, 2026
- adam-paterson/skillstheir own version, first seen Oct 11, 2026
- sponge-b0b/Polaristheir own version, first seen Aug 3, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- sponge-b0b/Polaris★ 4same name
- mazzsva/claude-skills★ 3same name
- adam-paterson/skills★ 1same name
- fclabs/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository26 other files it gives its agents.
- advise-tech-stackSkill
- commit-with-affectsSkill
- db-dev-guideSkill
- export-db-indexesSkill
- frontend-dev-guideSkill
- frontend-ux-evaluatorSkill
- generate-pr-descriptionSkill
- generate-test-from-impactSkill
- generate-test-skeletonSkill
- lock-global-conventionsSkill
- plan-component-hierarchySkill
- plan-page-mapSkill
- proposal-reviewSkill
- propose-workflow-improvementsSkill
- pr-self-reviewSkill
- record-decisionSkill
- review-guardrailsSkill
- run-pending-specsSkill
- run-testsSkill
- scan-bundle-bloatSkill
- scan-code-hygieneSkill
- scan-dead-routesSkill
- scan-frontend-qualitySkill
- scan-orphan-componentsSkill
- scan-unused-exportsSkill
- sync-llm-contextSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Read the ## Acceptance Criteria, ## 验收标准, or equivalent section.
- Distinctive: line 18
If no acceptance section exists, return:
- Distinctive: line 42
If it fails, inspect the relevant files and fix implementation.
- Very specific: line 45
After three failed repair attempts, return ✗ with the last error summary and request arbitration.
- Distinctive: line 47
Do not rewrite the spec to make verification easier.
- Distinctive: line 48
Do not weaken test assertions unless the spec explicitly says test expectations are still drafts.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Verify Spec
Input
Path to a completed spec-*.md.
Step 1: Extract Acceptance Criteria
Read the ## Acceptance Criteria, ## 验收标准, or equivalent section.
List every unchecked item (- [ ]) as an acceptance criterion.
If no acceptance section exists, return:
## Verification Results
- ○ No explicit acceptance criteria found; manual review requiredStep 2: Classify Each Criterion
| Type | Signals | Check |
| Test/build command | npm run, pytest, pnpm, yarn, go test, cargo test, mvn test, build, lint | Run command and inspect exit code |
| File content | exists, contains, does not contain, 不存在, 包含, 不出现 | Use test, rg, or equivalent |
| HTTP/API behavior | status, redirect, returns, response, 状态码, 返回 | Use local curl/http client when endpoint is available |
| Database/schema artifact | DDL, migration, ALTER TABLE, schema | Check generated migration/DDL files or run the configured schema command |
| Browser/visual/manual | browser, DevTools, Network, visual, screenshot, UX, 浏览器, 视觉 | Mark manual (○) |
| External service | third-party APIs, paid APIs, production-only services | Mark manual or mock-only (○) |
Step 3: Repair Failed Automatic Checks
For each automatic check:
- Run the check.
- Mark
✓if it passes. - If it fails, inspect the relevant files and fix implementation.
- Re-run only the failing check.
- Mark
✗→✓if the repair succeeds. - After three failed repair attempts, return
✗with the last error summary and request arbitration.
Do not rewrite the spec to make verification easier. Do not weaken test assertions unless the spec explicitly says test expectations are still drafts.
Step 4: Output
Return this exact shape for run-pending-specs to paste into the session:
## Verification Results
- ✓ npm run build passed
- ✗→✓ API returned 500 first; fixed missing null guard; now returns 200
- ○ Visual layout requires browser reviewLegend:
✓automatic check passed.✗→✓automatic check failed, implementation was fixed, then passed.✗automatic check still fails and needs arbitration.○cannot be automatically verified in this environment.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

