spec-compliance-auditor

Audit code against project specification files and generate compliance reports.

2|2|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/mathiasbourgoin/roster --skill spec-compliance-auditor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-compliance-auditor
Source: https://github.com/mathiasbourgoin/roster/tree/main/.opencode/skills/spec-compliance-auditor
Command: npx skills add https://github.com/mathiasbourgoin/roster --skill spec-compliance-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of implementation drift from project specifications, where code diverges from agreed requirements or spec items are left unimplemented, leading to unexpected behavior, rework, and missed project goals.

Core Features & Use Cases

  • Testable Claim Extraction: Automatically pulls concrete, verifiable requirements from a spec file (default kb/spec.md or a custom path provided via input) and numbers them for reference.
  • Implementation Verification: Checks each claim against actual code and existing tests, classifying status as pass, partial, diverge, or missing.
  • Unspecified Feature Detection: Flags implemented features that are not covered in the spec to identify gaps or unapproved additions.
  • Use Case: A development team can run this audit before a release to confirm all agreed spec requirements are implemented and tested, and no unapproved features were added to the codebase.

Quick Start

Use the spec-compliance-auditor skill to audit the current codebase against the project's spec file and generate a full compliance report.

Frequently Asked Questions about spec-compliance-auditor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify code matches project specifications before a release?

Spec compliance auditing checks each requirement extracted from your spec file against actual code and tests, classifying status as pass, partial, diverge, or missing. It flags unimplemented requirements and unspecified features added without approval.

How do I find unimplemented requirements and behavioral divergence in my codebase?

Spec gap analysis extracts verifiable requirements from a spec file, numbers them for reference, and checks each against actual code and tests. It flags unimplemented requirements, behavioral divergence, and unspecified features not covered in the spec.

What is the best way to audit implementation against formal spec documents?

Implementation auditing pulls verifiable requirements from a spec file and checks each claim against actual code and tests. It generates a structured compliance report with claim-level status, severity-ranked issues, and recommendations for code fixes or spec updates.

Can I use a custom spec file path for requirement verification instead of the default?

Yes, requirement verification supports custom spec file paths provided via input. If no custom path is supplied, the audit defaults to reading the specification from kb/spec.md.

Does spec gap analysis detect implemented features that are not covered in the spec?

Yes, unspecified feature detection flags implemented features not covered in the spec to identify gaps or unapproved additions. This catches unapproved codebase additions during the compliance audit.

What limitations should I consider before running a spec compliance audit?

Spec compliance auditing requires formal spec documents with concrete, testable claims. It is designed for development workflows where teams maintain formal specs and need to verify code alignment before releases or code reviews.