odylith-registry-spec-sync

To detect drift between registry specs and implementations, run a sync across your project. The Skill compares component specs against current code and governance artifacts, identifies inconsistencies, and outputs audit-ready reports with cross-reference mappings.

Registry spec sync aligns registry component specifications with their current implementations and governance evidence. You need it when specs drift from code or governance docs, causing misalignment across teams and making audits harder due to broken traceability links.

Yes, you can enforce YAML frontmatter metadata consistency across registry specs. The Skill checks frontmatter fields during the sync process and ensures metadata remains uniform across all component specs and their linked governance documentation.

To generate audit-ready reports for registry governance evidence, run a sync to collect evidence and detect drift across specs, code, and governance docs. The output includes cross-reference mappings and traceability links between implementations and governance decisions.

No, registry spec sync does not require any external dependencies or components. It operates independently across your project's code, governance docs, and artifact references to perform drift detection and evidence collection without additional setup.

The best way to maintain traceability links between specs and governance docs is to run periodic syncs. This enforces cross-links to implementation files, validates YAML frontmatter metadata, and outputs reports mapping specs to code and governance decisions.