spec-auditor

Audit technical specifications for defects, ambiguities, and inconsistencies across documents.

1|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/noelserdna/claude-plugin-sdd --skill spec-auditor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-auditor
Source: https://github.com/noelserdna/claude-plugin-sdd/tree/main/skills/spec-auditor
Command: npx skills add https://github.com/noelserdna/claude-plugin-sdd --skill spec-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the systematic auditing of specifications to detect defects, ambiguities, and inconsistencies across multiple documents, ensuring contracts remain true to intent.

Core Features & Use Cases

  • Cross-document audit: identify ambiguities, silent requirements, and semantic conflicts across domain, use-cases, workflows, invariants, and ADRs.
  • Report generation: produce precise audit findings with location, problem description, and resolution questions to guide corrective actions.
  • Traceability validation: verify LINKS among REQ → UC → WF → INV → ADR to maintain end-to-end traceability.

Quick Start

  • Run the spec-auditor in audit mode to generate an initial findings report.
  • Review the audit output, update specs to address critical findings, and add ADRs for architectural decisions.

Frequently Asked Questions about spec-auditor

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

FAQPage Schema
How do I audit technical specifications for cross-document inconsistencies?

Cross-document specification auditing detects defects, ambiguities, and inconsistencies across domain, use-case, workflow, invariant, and ADR documents. It generates an audit report with precise findings, locations, and resolution questions to guide corrective actions.

What is traceability validation for specification repositories?

Traceability validation verifies links among Requirements, Use Cases, Workflows, Invariants, and ADRs to maintain end-to-end document integrity. It enforces formal invariant definitions and glossary alignment to confirm specifications remain true to intent.

How do I identify silent requirements and ambiguities across spec documents?

Identifying silent requirements and ambiguities requires a cross-document audit analyzing domain specs, use-cases, workflows, invariants, and ADRs. It isolates semantic conflicts and generates resolution questions to guide corrective updates without proposing implementations.

Does the specification audit propose code implementations for defects found?

No, the specification audit does not propose code implementations for detected defects. It strictly produces audit findings with location details, problem descriptions, and resolution questions to guide manual corrective actions and architectural updates.

When do I need to run a cross-document specification audit?

You need a cross-document specification audit when a specification repository requires quality assurance and traceability validation. It verifies glossary alignment, enforces formal invariant definitions, and checks REQ to ADR traceability.