doc-validator
doc-validator enforces consistency rules across your entire SDD documentation corpus—catching broken links, orphaned artifacts, cumulative-tag gaps, duplicate IDs, and traceability gaps across all 8 layers. It runs declarative checks against your corpus structure and can optionally repair safely-fixable issues like missing reciprocal links or stale metadata. Use it before releases or after batch generation to ensure your documentation chain stays machine-verifiable and traceable.
doc-validator checks cross-document references, orphaned artifacts, and traceability across your SDD corpus.
AI-generated summary based on this skill's SKILL.md
Install
vladm3105/aidoc-flow-framework/doc-validator · repository language: Python
git clone https://github.com/vladm3105/aidoc-flow-framework
cp -r aidoc-flow-framework/platforms/claude-code-plugin/skills/doc-validator ~/.claude/skills/doc-validatorFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
What does doc-validator check for broken links in documentation?
doc-validator validates cross-document references across your entire SDD corpus, detecting broken links and orphaned artifacts. It checks bidirectional traceability between documents and can auto-fix safely-fixable issues like missing reciprocal links. The tool runs declarative checks against your corpus structure to ensure all references remain valid and traceable across all 8 layers.
How does doc-validator find orphaned artifacts in my docs?
doc-validator enforces cumulative-tag hierarchy rules and detects orphaned artifacts that lack proper parent references or layer assignments. It scans your entire documentation corpus to identify artifacts that fall outside expected structural patterns, helping you maintain a clean, fully-connected document graph before releases.
Can doc-validator validate traceability matrix completeness?
Yes. doc-validator checks bidirectional traceability and validates traceability depth across all layers. It detects gaps in your traceability matrix, ensures reciprocal links exist where required, and can optionally repair broken connections automatically. This keeps your documentation chain machine-verifiable and audit-ready.
Does doc-validator detect duplicate IDs in documentation?
doc-validator validates ID format compliance and detects duplicate identifiers across your corpus. It ensures all IDs follow your declared format rules and flags any duplicates that could break cross-references or traceability chains, helping prevent silent reference failures.
What quality checks does doc-validator run on prose and metadata?
doc-validator reviews prose quality, terminology consistency, and metadata accuracy across your documentation. It validates section counts, checks mermaid diagram consistency, and enforces documentation governance rules. Use it as a quality gate before releases to catch terminology drift and metadata staleness.
When should I run doc-validator on my corpus?
Run doc-validator before releases or after batch generation to ensure your documentation chain stays machine-verifiable. It's designed as a corpus validation and repair tool that catches structural issues early, preventing broken links and traceability gaps from reaching production.
SKILL.md
rendered from the published skill — quoted content, verbatim
doc-validator
Purpose
Validate relationships and consistency across documents in the SDD corpus:
broken cross-references, orphaned artifacts, one-way links, cumulative-tag
gaps, duplicate or malformed IDs, and traceability-matrix completeness across
the 8 layers. This skill is the validator — the framework ships no runtime
code; it applies declarative checks against ${CLAUDE_PLUGIN_ROOT}/framework/governance/ and the
layer README.md files.
Layer: cross-cutting utility (reads all 8 layers; produces no
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 1 file
platforms/claude-code-plugin/skills/doc-validator/SKILL.md