spec-verify
Skill9 starsChanged 4 months agoMITView on GitHub
Verify a completed implementation against its spec. Checks all acceptance criteria, runs tests, validates coverage. Use after spec-implement is done.
9 other projects use a version of this.
Adopted by
Most recently taken up by
- arfar-x/agent-skillstheir own version, first seen Nov 14, 2026
- orrrrli/ai-engineering-stacktheir own version, first seen Nov 1, 2026
- mahdyarief/spec-driven-agent-kittheir own version, first seen Nov 1, 2026
- orrrrli/clawd-harnesstheir own version, first seen Oct 20, 2026
- anxndsgn/skillstheir own version, first seen Sep 22, 2026
- cldanielhernandez/claude-skillstheir own version, first seen Aug 8, 2026
Used with
Projects with it also use grill-me and handoff.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- arfar-x/agent-skills★ 14same name
- orrrrli/ai-engineering-stack★ 2same name
- orrrrli/clawd-harness★ 2same name
- anxndsgn/skills★ 1same name
- rainmancswh-dot/claude-skills★ 1same name
- ba0918/claude-skills★ 0same name
- cldanielhernandez/claude-skills★ 0same name
- mahdyarief/spec-driven-agent-kit★ 0same name
- telefrek/vallorcine★ 0same 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 repository8 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- auth-implementationSkill
- incident-responseSkill
- kiro-railsSkill
- review-guideSkill
- spec-archiveSkill
- spec-implementSkill
- spec-proposeSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Verify that a completed implementation satisfies its spec.
- Distinctive: line 45
After checking, append a verification section to the spec folder:
- Distinctive: line 72
Check tests exist: - don't just trust that code works.
- Distinctive: line 73
Flag scope creep: - if implementation added things not in the spec, note it
“Common” is measured: kept by at least 6 in 10 of the 9 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
Spec Verify Workflow
Verify that a completed implementation satisfies its spec.
Steps
- Read the spec - load requirements.md and design.md
- Run verification checks against each requirement
- Generate a verification report
- Flag any gaps for remediation
Verification Checklist
For each requirement in requirements.md:
Functional Verification
- Every acceptance criterion has a passing test
- Edge cases identified in design.md are handled
- Error paths are tested (not just happy path)
Non-Functional Verification
- Performance requirements met (if specified)
- Security requirements met (no secrets, proper auth, input validation)
- Accessibility requirements met (if frontend)
Code Quality
- Tests pass (
npm test/pytest/ equivalent) - Type checking passes (if applicable)
- No lint errors
- No hardcoded values that should be configurable
Documentation
- Code comments explain WHY, not WHAT
- API changes documented
- ADR written if architectural decisions were made
- Changelog entry added
Verification Report
After checking, append a verification section to the spec folder:
<!-- Append to tasks.md -->
## Verification Results
**Date:** YYYY-MM-DD
**Status:** ✅ PASSED | ⚠️ PARTIAL | ❌ FAILED
### Requirements Coverage
| Requirement | Status | Notes |
|-------------|--------|-------|
| REQ-1 | ✅ | All criteria met |
| REQ-2 | ⚠️ | Missing edge case test |
### Gaps Found
- Gap 1: ...
- Gap 2: ...
### Recommendation
Ready for archive / Needs remediation on: ...Rules
- Be strict - a requirement is only "met" if ALL its acceptance criteria pass
- Check tests exist - don't just trust that code works; verify tests cover it
- Flag scope creep - if implementation added things not in the spec, note it
- Recommend next step - either
spec-archive(if passed) or remediation tasks
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.

