spec-compliance

Map RFC 2119 spec requirements to code and generate compliance reports.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/vr000m/skills.md --skill spec-compliance-vr000m
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-compliance
Source: https://github.com/vr000m/skills.md/tree/main/.codex/skills/spec-compliance
Command: npx skills add https://github.com/vr000m/skills.md --skill spec-compliance-vr000m

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of validating code against formal specifications by extracting normative requirements (MUST, SHOULD, MAY) and mapping them to code evidence to produce a clear compliance report.

Core Features & Use Cases

  • Extract normative requirements (MUST, SHALL, SHOULD, MAY) from RFCs, IETF drafts, and W3C/WHATWG specs.
  • Analyze code by searching for implementations, constants, and tests that satisfy each requirement, and generate a structured report with Met, Missing, Partial, and N/A classifications.
  • Use in code review and regulatory-compliance workflows to verify that changes align with spec requirements before merging.

Quick Start

Run a compliance check with a target code file and a spec reference to generate a report.

Frequently Asked Questions about spec-compliance

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

FAQPage Schema
How do I check if my code complies with RFC 2119 normative requirements?

To check code compliance with RFC 2119 normative requirements, this Skill extracts MUST, SHOULD, and MAY keywords from a specification and maps them to your codebase to generate a structured Met/Missing/Partial/N/A report.

Can I automate code reviews against W3C and WHATWG specifications?

You can automate code reviews against W3C and WHATWG specifications by fetching the target spec sections, extracting normative requirements, and analyzing your code for evidence of compliance before merging changes.

What is the best way to verify code coverage for IETF draft requirements?

The best way to verify code coverage for IETF draft requirements is to automate the mapping of extracted MUST and SHALL statements to specific code implementations, constants, and tests, which yields a structured compliance report.

Does this compliance check work with specific sections of a specification?

Yes, this compliance check works with specific sections of a specification by applying optional section scoping, allowing you to fetch the precise spec text and extract only the relevant normative requirements for analysis.

How are missing or partially implemented spec requirements reported?

Missing or partially implemented spec requirements are reported through a structured compliance report that classifies each extracted normative requirement as Met, Missing, Partial, or N/A based on the analyzed code evidence.

What do I need to generate a spec compliance report for my codebase?

To generate a spec compliance report for your codebase, you need to provide a target code file and a formal spec reference, such as an RFC, IETF draft, or W3C/WHATWG document, to initiate the automated check.