ui-docs-sync

To detect documentation drift between UI specs and repo docs, run an audit that discovers spec packages, verifies link coverage, and flags contradictions between spec claims and repository documentation without modifying files.

Checking if repository documentation references all UI specification packages involves scanning the codebase for spec packages and validating that relevant docs, product contracts, and route maps contain the necessary cross-artifact links.

UI spec and repo documentation consistency checking is a read-only verification process that compares primary factual claims from spec packages against repository documentation to surface missing links, stale references, and invisible drift items.

UI documentation sync does not modify your GitHub repository files; it operates as a read-only auditor that reports missing links, stale references, and unresolved blocker findings visible in the spec index.

You should run a UI spec package and repo documentation audit when creating or updating UI spec packages, changing documentation that describes UI behavior, onboarding agents, or recovering specs retroactively to ensure source-of-truth consistency.

Yes, you can use this to onboard agents that rely on repository documentation by verifying that agent instruction files and route maps consistently reference and match the UI specification packages defining each screen.