spec-governance
Skill286 starsChanged 5 months agoMITView on GitHub
Use when a round uses proposal/design/tasks/spec/archive artifacts or needs OpenSpec-style artifact validation without depending on the OpenSpec CLI.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- sarveshtalele/mcp-skills-registrytheir own version, first seen Jun 12, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- sarveshtalele/mcp-skills-registry★ 2same 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 repository18 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- agency-rosterSkill
- arcgenticSkill
- audit-roundSkill
- claude-code-session-brokerSkill
- close-roundSkill
- codex-thread-orchestrationSkill
- codify-lessonSkill
- cross-session-handoffSkill
- execute-roundSkill
- orchestrate-roundSkill
- plan-roundSkill
- pre-round-scanSkill
- session-modeSkill
- source-intakeSkill
- track-refsSkill
- using-arcgenticSkill
- verify-gatesSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Check that the change directory has proposal.md, design.md, tasks.md, and specs//*.md.
- Distinctive: line 29
Do not add an OpenSpec npm dependency.
- Very specific: line 30
Do not replace arcgentic's state machine with OpenSpec states.
≈ “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
spec-governance
Validates OpenSpec-style change artifacts as inputs to arcgentic planning, development, and audit.
Workflow
- Check that the change directory has
proposal.md,design.md,tasks.md, andspecs/**/*.md. - Count complete and incomplete tasks.
Validate archive readiness without moving files:
arcgentic spec-governance status openspec/changes/<change> arcgentic spec-governance validate openspec/changes/<change> arcgentic spec-governance archive openspec/changes/<change>- Map proposal/design/tasks/spec facts into handoff and audit facts.
Boundaries
- V1 archive is validate-only.
- Do not add an OpenSpec npm dependency.
- Do not replace arcgentic's state machine with OpenSpec states.
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.