speckit.validate
Skill3 starsChanged 59 days agoMITView on GitHub
Implementation Validator - Decide whether implementation satisfies spec, governance, build, runtime, and evidence gates.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- compnew2006/Spec-Kit-Antigravity-Skillstheir own version, first seen Jan 26, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- compnew2006/Spec-Kit-Antigravity-Skills★ 68same 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 repository64 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/bro-skills.mdcCursor rule
- .agents/skills/llms.txtllms.txt
- brandkitSkill
- bro-mcp-loopSkill
- ci-security-scanning-with-strixSkill
- design-taste-frontendSkill
- fix-security-vulnerabilities-with-strixSkill
- full-output-enforcementSkill
- gpt-tasteSkill
- high-end-visual-designSkill
- imagegen-frontend-mobileSkill
- imagegen-frontend-webSkill
- image-to-codeSkill
- industrial-brutalist-uiSkill
- managed-pentesting-with-strixSkill
- minimalist-uiSkill
- penetration-testing-with-strixSkill
- ponytailSkill
- redesign-existing-projectsSkill
- speckit.ai-engineerSkill
- speckit.analyzeSkill
- speckit.architectureSkill
- speckit.backendSkill
- speckit.backlogSkill
- speckit.checkerSkill
- speckit.checklistSkill
- speckit.clarifySkill
- speckit.constitutionSkill
- speckit.contentSkill
- speckit.databaseSkill
- speckit.dddSkill
- speckit.debugSkill
- speckit.devopsSkill
- speckit.diffSkill
- speckit.event-realtimeSkill
- speckit.frontendSkill
- speckit.game-embeddedSkill
- speckit.game-native-jsSkill
- speckit.geoSkill
- speckit.identity-accessSkill
- speckit.identitySkill
- speckit.implementSkill
- speckit.mapSkill
- speckit.migrateSkill
- speckit.payment-fintechSkill
- speckit.planSkill
- speckit.quizmeSkill
- speckit.reviewerSkill
- speckit.roadmapSkill
- speckit.securitySkill
- speckit.seoSkill
- speckit.specifySkill
- speckit.sre-observabilitySkill
- speckit.statusSkill
- speckit.tasksSkill
- speckit.taskstoissuesSkill
- speckit.testerSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
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
- Distinctive: line 10
Read spec, plan, tasks, source, constitution, project config, reports, and documented commands.
- Very specific: line 11
Write .agents/memory/validation-report.md with a requirement matrix, evidence links, blockers, limitations, and verdict.
- Distinctive: line 14
Verify task state and map every success criterion to implementation and evidence.
- Distinctive: line 16
Run applicable formatter, type-check, lint, test, build, migration, and security checks in Docker where required.
- Distinctive: line 17
Start runtime only when configured, wait on a bounded health/readiness condition, and inspect logs immediately on failure.
- Distinctive: line 18
Check constitution, ENV/secret handling, non-root runtime, accessibility/responsive evidence, and rollback/recovery requirements as …
- Distinctive: line 25
Read-only. Do not approve unfinished tasks, failed applicable checks, or unsupported assumptions.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Mission
Produce the final evidence-based validation verdict before release or handoff.
Inputs and Outputs
- Read spec, plan, tasks, source, constitution, project config, reports, and documented commands.
- Write
.agents/memory/validation-report.mdwith a requirement matrix, evidence links, blockers, limitations, and verdict.
Protocol
- Verify task state and map every success criterion to implementation and evidence; unchecked tasks or missing evidence are blockers.
- Discover project capabilities and mark non-applicable build, runtime, health, Docker, or framework checks as N/A with reason.
- Run applicable formatter, type-check, lint, test, build, migration, and security checks in Docker where required; capture exit codes and logs.
- Start runtime only when configured, wait on a bounded health/readiness condition, and inspect logs immediately on failure. Never use sleep alone as readiness proof.
- Check constitution, ENV/secret handling, non-root runtime, accessibility/responsive evidence, and rollback/recovery requirements as applicable.
- Verdict is PASS only when all applicable gates pass and no requirement lacks evidence; otherwise FAIL with severity, owner, and next action. N/A never counts as PASS.
Completion Gate
The report is reproducible, each claim cites evidence, limitations are explicit, and the verdict does not exceed what was actually verified.
Guard Rails
Read-only. Do not approve unfinished tasks, failed applicable checks, or unsupported assumptions. Do not treat a checkbox alone as delivery evidence.
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.

