consistency-check

To check for contradictions between BDD scenarios and OpenSpec specifications, cross-reference Gherkin feature files against requirements and glossary terms to surface behavioral inconsistencies and terminology mismatches across the codebase.

Documentation drift is the gradual mismatch between BDD feature files, OpenSpec specifications, and project docs, which introduces hidden behavioral contradictions and terminology inconsistencies that lead to bugs and confused users.

You audit terminology consistency by parsing the project glossary and cross-referencing its terms against English and zh-tw documentation, ensuring uniform naming conventions across all project files.

Yes, you can optionally triage coverage gaps by analyzing Go source code alongside BDD scenarios and OpenSpec specifications, classifying coverage gaps as untested, missing, or implemented differently.

You should run a cross-reference consistency check before a major release to verify that relational features described in the spec are exercised by tests and accurately reflected in the user guide.

Yes, consistency-check operates independently without external dependencies or components, parsing Markdown, Gherkin, and glossary files directly to generate a structured contradiction report.