opsx-spec-validate
Skill1 starsChanged 10 days agoMITView on GitHub
Use when you need to validate if your openspec artifacts violate any specs defined by openspec.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- vladcheck/skillsword for word, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 1
- vladcheck/skills★ 1100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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 repository19 other files it gives its agents.
- analyze-session-pingpong-logsSkill
- create-glossarySkill
- deepseek-reasoning-tier-clarifierSkill
- defineSkill
- find-alternativesSkill
- get-note-links-from-textSkill
- gitlab-eas-tickets-publishSkill
- gitlab-mr-roundtripSkill
- git-rebuild-branchSkill
- git-sequentialSkill
- gost-report-rebuildSkill
- mattpocock-skills-researchSkill
- mirea-moodle-downloadSkill
- obsidian-add-links-to-noteSkill
- paretto-principleSkill
- publish-spec-gitlab-milestoneSkill
- publish-tickets-gitlabSkill
- solidSkill
- update-skills-via-skills-shSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 36
Every requirement has at least one scenario
- Distinctive: line 39
No empty delta sections
- Distinctive: line 42
Every new capability in proposal.md → has spec file in specs/
- Distinctive: line 43
Every modified capability in proposal.md → has delta spec file in specs/
- Distinctive: line 44
No extra spec files without corresponding proposal entries
- Distinctive: line 45
No extra proposal entries without corresponding spec files
- Distinctive: line 49
Ask a subagent to verify if your specs violate openspec conventions
≈ “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
Files to check
- proposal.md - initial artifact
- design.md - builds on proposal.md
- specs/* - builds on proposal.md
- tasks.md - builds on every spec above
Rules for proposal.md
- Has sections: Why, What Changes, Capabilities (New + Modified), Impact
- Capabilities use kebab-case names
- Each new capability listed in New Capabilities has a corresponding spec file in specs/
- Each modified capability listed in Modified Capabilities has a corresponding delta spec file in specs/
- Breaking changes marked with BREAKING
- Concise (1-2 pages)
Rules for design.md
- Has sections: Context, Goals/Non-Goals, Decisions, Risks/Trade-offs, Migration Plan, Open Questions
- Each Decision explains rationale (why X over Y?)
- Risks have mitigation
- Migration Plan has concrete steps
- No empty sections
Rules for spec files (all)
- Scenario headers: exactly 4 hashtags (#### Scenario: ...)
- Requirement headers: exactly 3 hashtags (### Requirement: ...)
- Every requirement has at least one scenario
- SHALL/MUST for normative statements
- Delta section headers valid: only ## ADDED, ## MODIFIED, ## REMOVED, ## RENAMED
- No empty delta sections
Cross-artifact consistency
- Every new capability in proposal.md → has spec file in specs/
- Every modified capability in proposal.md → has delta spec file in specs/
- No extra spec files without corresponding proposal entries
- No extra proposal entries without corresponding spec files
Algorithm
- Ask a subagent to verify if your specs violate openspec conventions
- Fix violations
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.