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
Decision gist · record as of 2026-07-27
doc-validator checks cross-document references, orphaned artifacts, and traceability across your SDD corpus. 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.
Use it when
- doc-validator enforces cumulative-tag hierarchy rules and detects orphaned artifacts that lack proper parent references or layer.
- Yes.
Verify before relying
Read SKILL.md below before installing (1 file). Open directory: indexed for reading, not audited.
Install
vladm3105/aidoc-flow-framework/doc-validator · repository language: Python
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently 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)
File tree — 1 file
platforms/claude-code-plugin/skills/doc-validator/SKILL.md
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Validate cross-document references and detect broken links across SDD corpus”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
Quality-advisor gives live feedback while you create or review SDD documents, catching completion gaps, documentation anti-patterns, tag compliance, and naming issues before submission. It scores sections, detects common problems like missing traceability or broken links, validates cumulative tagging across layers, and returns actionable recommendations to fix issues.
doc-bdd translates EARS requirements into Layer 4 acceptance scenarios using structured YAML (not Gherkin), each with Given-When-Then phases, element-level trace links to upstream EARS, and forward mapping to SPEC sections. Use this after EARS is complete and before ADR/SPEC authoring; for batch generation across multiple documents, the autopilot skill handles orchestration.
doc-adr captures a single architectural decision using the Context-Decision-Consequences pattern, positioned as Layer 5 in the specification-driven development flow. It records the rationale, chosen approach, evaluated alternatives, and accepted trade-offs for decisions that bridge container and component design.
Automates the full ADR lifecycle from source documents (BRD, PRD, EARS, BDD) or free-text prompts through generation, validation, and iterative refinement. Detects whether an ADR exists, routes to generation or review-and-fix accordingly, and maintains the ADR index with passing scores. Supports single or batch processing with configurable quality thresholds and fix iteration limits.
gate-check automates the verification step in the change governance process by selecting the correct approval gate based on affected layers, running its entry criteria and error checks, and populating the approval form for human sign-off. It verifies but never approves—all signature and decision fields remain blank for the designated approvers.
project-adopt brings an established codebase into the Specification-Driven Development workflow by detecting existing code and documentation, inferring the domain, and scaffolding the 8-layer artifact structure. It reverse-engineers baseline artifacts from your running system at draft status, seeding the SDD backbone in one setup pass. Hand off to doc-flow and per-layer audits to close gaps and promote drafts to ready.
More skills doc-adr-fixer (MIT)