doc-validator

Documentation traceability validation checks internal links, ID formats, and forward/backward consistency chains across BRD, PRD, EARS, BDD, ADR, SYS, REQ, IMPL, CTR, SPEC, TASKS, and IPLAN documents. Use doc-validator to detect broken cross-references, orphaned artifacts, and bidirectional traceability gaps automatically before committing.

Yes, doc-validator performs token count validation against AI tool limits using tiktoken, flagging documents that exceed thresholds. It simultaneously enforces objective, factual language standards and identifies subjective claims that could affect downstream AI processing.

Traceability matrix validation ensures all requirements have source references and validates complete forward/backward chains (e.g., REQ → BDD → TASK). It enforces bidirectional consistency, detects duplicate IDs, and identifies orphaned requirements without proper connection points.

Doc-validator applies strict ID format validation across all documents, enforcing conventions like REQ-AUTH-001. Graph traversal and cross-reference validation detect malformed IDs and broken links, providing fix suggestions for immediate remediation.

Yes, doc-validator verifies both internal links and external file references as part of its cross-reference validation. It flags broken or incorrect file paths and ensures all references conform to project-wide ID and naming standards.

Doc-validator detects orphaned artifacts—requirements without proper source or downstream traceability—and identifies gaps in cross-document chains. It reports these violations with specific artifact IDs and layer information, enabling targeted remediation before document commit.