ambiguity-auditor

To check a knowledge base for contradictions and undefined terms, you can audit your specification files and glossary entries to identify vague requirements and cross-file inconsistencies. This process scans all files to flag undefined domain terms and inconsistent usage against the glossary.

Documentation staleness detection flags knowledge base files not updated in over 30 days and identifies references to removed codebase components. You need it before major feature releases to catch misaligned specs and outdated material that cause developer confusion and delayed delivery.

To audit cross-file consistency in specification markdown files, cross-reference claims across architecture docs and glossary definitions to detect contradictions. This validates cross-spec entity consistency and identifies missing cross-references to related concepts.

Yes, you can validate unquantified requirements in engineering specs. The audit scans knowledge base files to flag vague unquantified requirements and provides suggested measurable replacements to ensure clear, testable criteria for product and engineering teams.

Yes, the knowledge base audit works without external dependencies. It directly scans your structured knowledge base files including glossary entries and specification markdown files to generate a structured severity-ranked report of all findings with specific remediation recommendations.