grill-with-docs

To validate project terminology against a CONTEXT.md glossary, use the grill-detect.sh script to scan context and surface contradictions between code and plans. This prevents vague terms by checking your plan against existing defined vocabulary.

You can generate ADRs for non-trivial design decisions by running grill-suggest-adr.sh to vet decisions and grill-create-adr.sh to create them. This workflow triggers when terminology contradictions or significant design choices are detected during validation.

Terminology governance in DEVORQ-driven development is the process of guarding vocabulary consistency using a CONTEXT.md glossary. It validates plans against defined terms, detects code contradictions, and integrates as a non-blocking GATE-0 warn to guide teams without halting progress.

Yes, you can use shell scripts like grill-detect.sh to detect contradictions between code and project plans. The script scans for terminology mismatches against your CONTEXT.md glossary and proposes ADRs when the detected design decisions qualify.

Yes, you need a CONTEXT.md file or existing code to initialize terminology scanning. The grill-init-context.sh script sets up the required glossary environment, enabling detection and ADR generation for DEVORQ-driven contexts.

You should expect a breaking signal during terminology validation when the grill-detect.sh script finds severe contradictions between your plan and the CONTEXT.md glossary. Integrated as a non-blocking GATE-0, it issues warnings or breaks to guide teams on vocabulary issues.