spec-compliance-audit

Verify documented claims against code behavior to surface spec-to-code discrepancies.

276|56|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/PlamenTSV/plamen --skill spec-compliance-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-compliance-audit
Source: https://github.com/PlamenTSV/plamen/tree/main/agents/skills/niche/spec-compliance-audit
Command: npx skills add https://github.com/PlamenTSV/plamen --skill spec-compliance-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reconciling documentation claims with code behavior to surface spec-to-code discrepancies during audits.

Core Features & Use Cases

  • Spec-to-code verification: Detects when design documents, whitepapers, or design specs claim behavior not implemented or contradicts code.
  • Audit workflow automation: Orchestrates claim extraction, code verification, divergence classification, and reporting in one pass.
  • Use Case: In a security audit, run this agent to identify HAS_DOCS claims and verify corresponding implementations across the repository.

Quick Start

Trigger the Spec Compliance Audit agent on the target repository to begin the verification workflow.

Frequently Asked Questions about spec-compliance-audit

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

FAQPage Schema
How do I automate spec-to-code compliance checks for a smart contract audit?

Spec-to-code compliance checks detect discrepancies by extracting claims from design documents, mapping them to code behavior, classifying divergences, and generating a structured findings report. This verifies that documented behavior matches actual code implementation.

What is spec-to-code verification and when do I need it for a codebase?

Spec-to-code verification is the process of reconciling documentation claims with code behavior to surface discrepancies during audits. You need it when auditing multi-chain protocols or codebases with design specifications to ensure implementation matches documented claims.

How do I verify whitepaper claims against actual code behavior in a multi-chain protocol?

Verifying whitepaper claims against code behavior involves extracting claims from documentation, mapping them to code implementations, and classifying divergences. This autonomous audit workflow identifies HAS_DOCS claims and verifies corresponding implementations across the repository.

Can I use automated compliance audits for codebases with design documents and specifications?

Yes, automated compliance audits apply to codebases with design documents and specifications. The agent orchestrates claim extraction, code verification, divergence classification, and reporting in one pass to detect when design specs claim behavior not implemented or contradicted by code.

What is the best way to detect documentation claims that contradict code during a security audit?

The best way to detect contradicting documentation claims is running an autonomous spec compliance audit that extracts claims from docs, maps them to code, and classifies divergences. This surfaces discrepancies between documented behavior and code implementation during security audits.