verification
Skill0 starsChanged 2 months agoMITView on GitHub
Verify requirements, FSD boundaries, checks, and readiness evidence.
47 other projects use a version of this.
Adopted by
Most recently taken up by
- neuraforge-cl-es/adaptive-engineeringtheir own version, first seen Nov 8, 2026
- facebook/docusaurustheir own version, first seen Nov 8, 2026
- maideps/ai-harness-frameworktheir own version, first seen Nov 8, 2026
- Lanqiao-Luca/ai-java-workflowtheir own version, first seen Nov 8, 2026
- Beskars-Code/Skillstheir own version, first seen Nov 6, 2026
- Gabriel-Lafrance/Skillstheir own version, first seen Nov 6, 2026
Used with
Projects with it also use evidence-driven-writing, experiment-results-planning and 10 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.
Norman-burySkillevidence-driven-writing
Use when writing or revising Introduction, Related Work, background, literature synthesis, or any section where references must drive claims
Also in 3 projects that use this
- Norman-burySkill
experiment-results-planning
Use when designing experiments, result tables, mock planning data, evaluation protocols, or results sections before real data are final
Also in 3 projects that use this
- +10 more from Norman-bury
Other versions47 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 47
- facebook/docusaurus★ 67ksame name
- open-metadata/OpenMetadata★ 16ksame name
- openai/plugins★ 7.8ksame name
- hi-godot/godot-ai★ 3.4ksame name
- Norman-bury/research-writing-skill★ 3.4ksame name
- Norman-bury/articlewriting-skill★ 3.4ksame name
- forcedotcom/salesforcedx-vscode★ 1ksame name
- vercel/vercel-plugin★ 328same name
- s3s-project/s3s★ 315same name
- project-numina/numina-lean-agent★ 279same name
37 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 repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- architecture-decisionSkill
- developer-handoffSkill
- react-fsd-pocSkill
- backendSkill
- component-designSkill
- databaseSkill
- devopsSkill
- prototypeSkill
- supabaseSkill
- testingSkill
- acceptance-criteriaSkill
- product-definitionSkill
- product-discoverySkill
- project-analysisSkill
- user-storySkill
- ux-flowSkill
- validationSkill
- security-reviewSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 9 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 39 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Use when the task matches: verification, PREVIEW_READY, evidence.
- Distinctive: line 25
Check product requirement still matches the change.
- Distinctive: line 27
Run applicable checks: architecture/FSD, typecheck, lint, tests, build, runtime journeys, Preview when supported.
- Distinctive: line 30
Never invent test results, build results, Preview URLs, or security outcomes.
- Distinctive: line 31
Never say "everything works" unless the relevant checks actually ran and passed.
- Distinctive: line 43
Keep Product validation and engineering verification distinct.
- Distinctive: line 44
Do not claim completion without evidence.
- Distinctive: line 49
Do not skip FSD or security review for prototype only.
- Distinctive: line 50
Do not replace Product validation with this skill.
- Distinctive: line 51
Do not fabricate Preview URLs or deployment status.
“Common” is measured: kept by at least 6 in 10 of the 39 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
verification
When to use
Use when the task matches: verification, PREVIEW_READY, evidence.
Purpose
Prove engineering and product evidence before gates, separate from Product validation.
Inputs
- Acceptance criteria
- Runnable implementation
- Change scope
- Architecture decision
Process
- Check product requirement still matches the change.
- Observe acceptance journeys; do not rely on code reading alone.
- Run applicable checks: architecture/FSD, typecheck, lint, tests, build, runtime journeys, Preview when supported.
- For each check, record one of: passed, failed, or NOT RUN (with reason).
- Record VERIFY_FAILED or VERIFY_BLOCKED honestly.
- Never invent test results, build results, Preview URLs, or security outcomes.
- Never say "everything works" unless the relevant checks actually ran and passed.
Outputs
- Verification evidence (including NOT RUN items)
- Gate verdict
- Open risks
- Preview URL only when a Preview was actually created and verified
Verification
- Confirm each output exists and is reviewable.
- Keep Product validation and engineering verification distinct.
- Do not claim completion without evidence.
Restrictions
- Do not claim completion without evidence.
- Do not skip FSD or security review for prototype only.
- Do not replace Product validation with this skill.
- Do not fabricate Preview URLs or deployment status.
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.