trace-check

Traceability validation ensures bidirectional consistency between Business, Architecture, Requirements, and Testing artifacts. This Skill scans all SDD documents, verifies upstream/downstream link symmetry, validates ID formats, resolves broken markdown links and anchors, and auto-fixes minor issues while reporting compliance gaps.

Cumulative tagging requires each artifact to inherit and include all tags from previous functional layers, creating an unbroken chain of traceability. This prevents audit trail gaps and enables impact analysis by ensuring every requirement traces back through architecture to business objectives.

CTR dual-file compliance checks that every API contract artifact has both `.md` and `.yaml` files with matching slugs and valid schemas. This Skill validates the pairing automatically, ensuring contract definitions are complete and consistent across documentation and specification formats.

This Skill performs automatic backup and auto-fix of minor traceability issues while flagging critical non-compliance for manual review. You control the strictness level and choose which fixes to apply, balancing automation with oversight.

Traceability validation applies to markdown documents, YAML schema files, and structured SDD artifacts across Business, Architecture, Requirements, and Testing layers. It validates markdown links, anchors, ID hierarchies, and ensures all artifacts follow defined tag and format conventions.

Run traceability validation before regulatory audits, major releases, or when updating requirements and architecture. Automated scanning identifies broken links, missing tags, and format violations early, reducing rework and audit risk.