# Spec Governance

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

- Skill: `sarveshtalele/spec-governance` (Agent Skill, multi-file: 8 files)
- Install (CLI): `npx skillmds@latest add sarveshtalele/spec-governance`
- Raw SKILL.md: https://api.skillmd.com/api/skills/sarveshtalele/spec-governance/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- License: MIT
- Author: sarveshtalele (https://skillmd.com/u/sarveshtalele)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/sarveshtalele/spec-governance

---


# 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/`.