af-enforce-glossary

You enforce glossary compliance by validating domain terminology in BDD scenarios against a canonical glossary list, ensuring consistent language and preventing undefined terms in specifications and documentation.

Terminology validation is the process of checking that all technical terms used in feature specifications align with an official project glossary, preventing ambiguity and improving clarity across documentation.

You check term alignment by running a validation process against a structured glossary file, verifying that every domain-specific term in your BDD scenarios matches defined language rules and canonical entries.

Yes, a structured glossary file is required as a reference to validate domain terminology, serving as the canonical list that all terms in your BDD scenarios and documentation must adhere to.

The best way to maintain consistent language is to apply terminology validation during specification creation and review, checking all domain terms against a structured glossary to enforce unified language rules.

Yes, glossary validation applies to both creating and reviewing specifications, ensuring that new and existing BDD scenarios adhere to defined language rules and use only terms from the canonical glossary.