spec-audit
Skill6 starsChanged 15 days agoLicence not identifiedView on GitHub
Audits requirements and test plans (specs, tickets, user stories, acceptance criteria, test-plan docs) against a 1100+ rule QA catalog plus qa-pilot's own rules, cross-checks every claim against the code and existing tests, fills an entity card of must-check web patterns (e.g. modify vs delete, modal closing before its request) for every lifecycle entity, and writes a bucketed action list (Must / Should ≤8 / Highlight; bugs to fix then test, tests with level and target, product questions; filtered risks listed) as Markdown + JSON plus a P1/P2/P3 evidence report. Depth: critical | standard | thorough. Use when the user asks "what test cases are we missing for this flow", "review/audit the spec/requirements/AC", "проверь требования", "каких тест-кейсов не хватает", "насколько покрыт флоу", or wants a requirements-quality check before planning tests. Requires docs/qa/project-profile.md (run qa-pilot:onboard first). Not for one task's diff (use qa-pilot:task-qa) or the test code (use qa-pilot:test-code-audit).
5 other projects use a version of this.
Adopted by
Most recently taken up by
- Fadi88/one-man-startuptheir own version, first seen Oct 15, 2026
- pierre-lecocq/claude-skillstheir own version, first seen Oct 11, 2026
- khivi/cockpittheir own version, first seen Oct 5, 2026
- jsulmont/mcp-lisptheir own version, first seen Jun 27, 2026
- caseyng/Claude-skillstheir own version, first seen May 22, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- Fadi88/one-man-startup★ 16same name
- jsulmont/mcp-lisp★ 9same name
- caseyng/Claude-skills★ 1same name
- khivi/cockpit★ 0same name
- pierre-lecocq/claude-skills★ 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 repository11 other files it gives its agents.
- auditSkill
- coverSkill
- exploreSkill
- onboardSkill
- plan-testsSkill
- project-auditSkill
- task-qaSkill
- test-code-auditSkill
- testSkill
- ui-test-auditSkill
- write-testsSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
25 rules. 0 are common, 13 are distinctive, and 12 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
13
Distinctive
This author's own choices. Worth a look.
12
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 5 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.