spec-compliance

Verify code and test compliance with specified requirements using regex and semantic analysis.

Updated Jun 29, 2026

Search Tags:#quality assurance #static analysis #code review #specification compliance #test suite analysis

Ready to run

npx skills add https://github.com/handbrianc/skill-library --skill spec-compliance-handbrianc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-compliance
Source: https://github.com/handbrianc/skill-library/tree/main/skills/spec-compliance
Command: npx skills add https://github.com/handbrianc/skill-library --skill spec-compliance-handbrianc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill verifies that code and tests meet specifications, ensuring quality and reliability in software development processes.

Core Features & Use Cases

Spec Compliance Check: Verify that implementation matches the specifications in openspec/ or specs/ folders.
Requirement Extraction: Parse individual requirement statements from spec files.
Two-Axis Compliance Model: Assess both code and test compliance.
Six Phases: Systematic approach for discovering, extracting, checking, and reporting on spec compliance.
Compliance Reporting: Generate a prioritized, actionable report.

Quick Start

Run the spec-compliance skill to perform a spec compliance check on the current repository.

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 and tests comply with project specifications?▼

Spec compliance checking parses requirement statements from specification files and uses semantic analysis to verify your codebase and test suite match those requirements, generating a prioritized compliance report.

What is the two-axis compliance model for software quality assurance?▼

The two-axis compliance model assesses software quality by evaluating both code compliance and test compliance separately against extracted requirements, ensuring that the implementation functions correctly and the test suite adequately covers the specifications.

How do I extract individual requirements from spec files for code review?▼

Requirement extraction uses regex parsing to identify and isolate individual requirement statements within specification files, typically located in openspec or specs directories, preparing them for semantic compliance analysis.

Does static analysis for spec compliance require access to code history?▼

Yes, verifying specification compliance requires access to the project codebase, associated spec files, code history, and the test suite to accurately determine if the implementation and tests meet the specified requirements.

What is the best way to generate an actionable compliance report for my repository?▼

Generating an actionable compliance report involves a systematic six-phase approach that discovers specs, extracts requirements, checks code and test compliance, and prioritizes findings into a report detailing where the implementation fails to meet specifications.