requirements-auditor
Skill7 starsChanged 6 months agoMITView on GitHub
Use when checking requirements for ambiguity, contradiction, unverifiability, scope creep, missing trace links, or premature design decisions.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Key-of-door/Threshold-capabilitytheir own version, first seen Sep 17, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Key-of-door/Threshold-capability★ 1same 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.
- AGENTS.mdAGENTS.md
- conops-builderSkill
- decision-analysisSkill
- integration-plannerSkill
- requirements-distillerSkill
- technical-assessment-loopSkill
- validation-plannerSkill
- verification-plannerSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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 8
Use this skill to find requirement defects before implementation turns them into bugs.
- Distinctive: line 14
Check each true requirement has one obligation, owner/approver, source, rationale, acceptance condition, and verification method.
- Distinctive: line 15
Check traceability to user intent, CONOPS, source material, repo constraints, or parent requirement.
- Very specific: line 22
Start with references/source-grounding.md, then inspect Section 4.2 pages extraction/pages/page_067.md through extraction/pages/page_068.md …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Requirements Auditor
Use this skill to find requirement defects before implementation turns them into bugs.
Workflow
- Classify each statement: goal, measurable objective, requirement, constraint, assumption, or implementation choice.
- Reject requirements that are compound, vague, unverifiable, ownerless, sourceless, or design-prescriptive without justification.
- Check each true requirement has one obligation, owner/approver, source, rationale, acceptance condition, and verification method.
- Check traceability to user intent, CONOPS, source material, repo constraints, or parent requirement.
- Identify contradictions, missing requirements, unstable assumptions, TBD/TBR values, and interface gaps.
- Separate must-fix findings from questions and acceptable residual risk.
- Output an audit report ordered by implementation risk: finding, affected requirement, evidence, impact, correction.
Source grounding
Start with references/source-grounding.md, then inspect Section 4.2 pages extraction/pages/page_067.md through extraction/pages/page_068.md and Appendix C pages extraction/pages/page_207.md through extraction/pages/page_209.md before making requirement-quality claims.
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.