spec-verify
Skill0 starsChanged 4 months agoLicence not identifiedView on GitHub
Extract the verifiable contracts buried in natural-language specifications and documents, canonicalize them as clause schema v1, generate property-based tests (PBT), and mechanically detect drift between specification and implementation through evidence-based assurance levels. The first argument selects the workflow, formalize (extract contracts into clauses) / bind (generate PBT from clauses) / drift-check (lint plus traceability inspection) / self-test (measure detection power through mutation) / docgen (generate a read-only Markdown specification view). With no argument it guides you toward formalize when specs/clauses/ has no clause file, and runs drift-check when it does. Use when the user says "spec-verify", "verify the specification", "extract the contracts", "detect drift", "turn this into clauses", "generate PBT", or "generate the specification view". Unlike review-testing (test suite quality) and doc-check (docs-to-code consistency), it owns canonicalizing contracts and detecting drift.
11 other projects use a version of this.
Adopted by
Most recently taken up by
- benjaminthomas/spec-driven-devtheir own version, first seen Nov 8, 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
- arfar-x/agent-skillstheir own version, first seen Oct 12, 2026
- anxndsgn/skillstheir own version, first seen Sep 22, 2026
Used with
Projects with it also use spec-apply, spec-archive and 1 more.
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.
pivoshenkoSkillspec-apply
Implement an OpenSpec change's tasks in parallel - read the task queue, plan file-disjoint waves, dispatch one agent per task into its own worktree, verify, tick the checkbox, commit, repeat. Use when the user says "apply the change", "implement the change", "run the tasks", "work the tasks in parallel", "fan out the change", "dispatch the spec", "/spec-apply", or hands over an OpenSpec change and expects code written for it. Wraps `/opsx:apply`, whose loop is strictly serial, single-agent, and git-blind. Boundaries: artifacts missing or incomplete -> `spec-propose`; every task already ticked and the result needs checking -> `spec-verify`; a finished change ready to fold into the specs -> `spec-archive`; a plain GitHub issue with no OpenSpec change behind it -> `git-issue-start`.
Also in 3 projects that use this
sourjyaSkillspec-archive
Archive a completed and verified spec. Moves it from active specs to the docs archive, updates the spec registry. Use after spec-verify passes.
Also in 3 projects that use this
GoogleSkillgrill-me
A relentless interview to sharpen a plan or design.
Also in 3 projects that use this
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- arfar-x/agent-skills★ 14same name
- sourjya/kiro-rails★ 9same name
- pivoshenko/pivoshenko.ai★ 6same name
- benjaminthomas/spec-driven-dev★ 2same name
- orrrrli/ai-engineering-stack★ 2same name
- orrrrli/clawd-harness★ 2same name
- anxndsgn/skills★ 1same name
- rainmancswh-dot/claude-skills★ 1same name
- cldanielhernandez/claude-skills★ 0same name
- mahdyarief/spec-driven-agent-kit★ 0same name
1 more not listed
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 repository51 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- releaseSkill
- artifactsSkill
- attack-reviewSkill
- brainstormSkill
- briefSkill
- codebase-reviewSkill
- commitSkill
- context-auditSkill
- cycleSkill
- decision-journalSkill
- design-generateSkill
- design-guideSkill
- design-lintSkill
- design-scaffoldSkill
- design-validateSkill
- doc-auditSkill
- doc-checkSkill
- doc-writeSkill
- empirical-prompt-tuningSkill
- generate-review-rulesSkill
- github-issueSkill
- goal-decompositionSkill
- goal-loopSkill
- handoffSkill
- investigateSkill
- issueSkill
- iterateSkill
- ledgerSkill
- loop-triageSkill
- migrate-cycles-to-plansSkill
- mockup-diffSkill
- parallel-cycleSkill
- plan-implementSkill
- plan-reviewerSkill
- planSkill
- problem-solvingSkill
- refactorSkill
- review-depsSkill
- review-testingSkill
- sharedSkill
- skill-improveSkill
- skill-interface-auditSkill
- skill-regressionSkill
- skill-reviewerSkill
- sweep-fixSkill
- systematic-debuggingSkill
- test-driven-developmentSkill
- trigger-evalSkill
- using-workflowSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
17 rules. 0 are common, 9 are distinctive, and 8 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 11 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.
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.