spec-compliance

Verify codebase implementation of spec.md acceptance criteria with structured compliance reports.

21|5|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/aws-samples/sample-agent-greenhouse --skill spec-compliance-aws-samples
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-compliance
Source: https://github.com/aws-samples/sample-agent-greenhouse/tree/main/src/platform_agent/plato/skills/spec_compliance
Command: npx skills add https://github.com/aws-samples/sample-agent-greenhouse --skill spec-compliance-aws-samples

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifies that a codebase implements the acceptance criteria defined in spec.md, enabling deterministic audits of requirement coverage and traceability between specifications and implementation.

Core Features & Use Cases

  • Extract AC-xxx criteria from spec.md and map them to repository evidence (code and tests).
  • Generate a structured compliance report with per-AC status (PASS/PARTIAL/NOT_FOUND) and references to implementation files and tests.
  • Validate across multiple languages/projects by querying repo contents and tests, including cross-references like TC-xxx.

Quick Start

Run the spec-compliance check on your repository to produce a structured compliance report.

Frequently Asked Questions about spec-compliance

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

FAQPage Schema
How do I verify codebase compliance against spec.md acceptance criteria?

Spec compliance checks work by extracting AC-xxx criteria from spec.md and querying repository contents to locate matching implementation files and tests. It then cross-references TC-xxx test cases to produce a structured compliance report with PASS, PARTIAL, or NOT_FOUND statuses.

Can I check spec compliance for repositories with multiple programming languages?

Spec compliance checks support multiple languages and projects by querying repository contents and tests directly to locate AC-xxx and TC-xxx cross-references, ensuring requirement traceability regardless of the specific programming language.

What is the best way to automate requirement traceability between specifications and code?

Automating requirement traceability is best achieved by running a spec compliance check that scans your repository for AC-xxx and TC-xxx references, outputting a structured report mapping each acceptance criterion to its implementation and test evidence.

What does PARTIAL status mean in a spec compliance report?

In a spec compliance report, PARTIAL status indicates that an acceptance criterion has incomplete evidence in the repository, distinguishing it from PASS where full implementation and test evidence are found, and NOT_FOUND where no references exist.

Do I need a spec.md file to run automated codebase compliance checks?

You need a spec.md file containing defined AC-xxx acceptance criteria to run automated codebase compliance checks, as the tool requires this file to extract requirements and map them against your source files and tests for evidence.