agentleFS
sarveshtalelesarveshtalele/mcp-skills-registry/skills/factory/spec-governance/SKILL.md

spec-governance

Skill2 starsChanged 5 months agoMITView on GitHub

Validate a set of engineering artifacts against governance rules and emit a deterministic pass/fail audit report with a compliance score. Trigger on: governance check, compliance audit, validate spec, gate, review compliance.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 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.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before a release gate. Triggers: *governance check, compliance audit, validate spec, gate, review compliance*.

    line 45

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

spec-governance

Validate engineering artifacts against governance rules and emit a deterministic pass/fail audit with a compliance score.

When to use

Before a release gate. Triggers: governance check, compliance audit, validate spec, gate, review compliance.

Inputs

  • artifacts_present (array of strings, required) — e.g. spec.md, plan.md, tests.
  • spec_text (string, optional) — scanned for required sections.

Outputs

  • audit_markdown — the report.
  • score (0–100), passed (bool, threshold 70).

How it works

Each required artifact carries a weight (see governance_rules/rules.yaml); present artifacts accumulate score. Optional spec-section checks add detail. The gate passes at ≥ 70.

User stories

  • As a gatekeeper, I get an objective, repeatable pass/fail with reasons.

Edge cases

  • Artifact names are matched loosely (substring) to tolerate path prefixes.
  • Missing spec_text → section checks are skipped, not failed.

Files

See DOCS.md. Rules live in governance_rules/, report layout in audit_templates/.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.