spec-governance

Files (8)

• DOCS.md
• SKILL.md
• audit.md.tpl · audit_templates/
• rules.yaml · governance_rules/
• manifest.yaml
• __init__.py · scripts/
• main.py · scripts/
• test_skill.py · tests/

SKILL.md (first lines)

# 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](DOCS.md). Rules live in `governance_rules/`, report layout in `audit_templates/`.

From sarveshtalele/mcp-skills-registry, MIT.

More from sarveshtalele/mcp-skills-registry