design-doc-audit

You can check if design documents match the current codebase by running an audit that verifies consistency and identifies drift in file inventories, type/API accuracy, and behavioral claims.

Documentation drift detection is the process of identifying discrepancies and stale information in design documents by verifying specific architectural claims against the actual source code. This prevents misunderstandings before code merges.

You can audit a design doc against source code for a specific domain by running the consistency check in a domain-scoped mode. This targets the audit to relevant sections rather than scanning the entire project.

Yes, you can verify behavioral claims in documentation against actual code. The audit process specifically checks architectural statements and behavioral claims to ensure your docs accurately reflect the implemented logic.

The best way to find missing documentation coverage is to run a full audit using parallel specialist agents. This identifies discrepancies and stale information, flagging any inconsistencies between new code and existing design documents.

Yes, the design doc audit works with incremental code changes. It operates in incremental, full, or domain-scoped modes to verify file inventories and API accuracy, efficiently targeting only the modified code areas.