skill-usage-audit

To audit artefact frontmatter for governance compliance, scan Epic and Story files located under contexts/artefacts to verify required attestations like skills_invoked and related_decs. The process produces a per-artefact pass/fail report and an overall compliance rate suitable for release gates.

Frontmatter governance validation is the process of checking that Epic and Story artefacts declare required attestations such as skills_invoked and related_decs. It flags non-compliant items for remediation, ensuring artefacts meet governance standards before releases.

You can generate a compliance report for artefacts before a release by running an on-demand audit after a discovery session. The audit scans frontmatter fields, produces a structured pass/fail output, and generates a remediation list to guide necessary fixes.

Yes, you can validate expected skills_invoked values in artefact frontmatter by scanning for specific expected values such as generate-epics or generate-stories. The audit verifies these fields against the expected attestations and flags mismatches in the structured output.

You need to run a governance audit on artefact frontmatter prior to milestones or after discovery sessions. This ensures that all Epic and Story artefacts contain the required skills_invoked and related_decs attestations, producing an overall compliance rate to gate releases.

Automated frontmatter compliance checks for artefacts are limited to validating the presence and expected values of specific fields like skills_invoked and related_decs. They operate strictly on Epic and Story artefacts under contexts/artefacts and do not assess qualitative governance aspects.