subagent-doc-check

To detect documentation drift, compare code facts, documentation facts, and rule-chain facts across routes, feature modules, hooks, types, schema artifacts, and guidance files. Validating consistency across these diverse data sources identifies discrepancies and reports drift without altering code.

Code and documentation consistency validation is the process of scanning repository artifacts like routes, feature modules, schema changelogs, and status boards to verify that implementation details match their documented facts. It generates structured reports detailing identified drift without altering code.

Yes, you can check if a new feature module is in sync by gathering facts from the code, docs, and rule-chain independently. The validation compares these collected facts to identify discrepancies across status boards, parity matrices, and schema artifacts.

You report code and documentation inconsistencies by scanning the repository for drift across guidance files, hooks, and types, then generating a structured report detailing the identified discrepancies. This validation process operates independently and does not alter code.

The best way to validate rule-chain facts against repository documentation is to collect facts independently from rules, code, and docs, then compare them across schema artifacts and parity matrices. This ensures a unified and accurate representation of the project's state.