grill-with-docs

To stress-test a feature plan against domain documentation, you undergo an iterative, one-question-at-a-time interview that cross-references your plan with your repository's glossary and documented decisions to eliminate terminology drift and hidden contradictions.

The best way to detect terminology drift is by cross-referencing the codebase against your proposed wording to find contradictions, automatically flagging conflicts when terms disagree with your documented domain model.

You clarify requirements and boundaries for integration discussions by using scenario-based boundary testing, probing edge cases and relationship cardinalities with concrete examples to define what is in-scope versus out-of-scope.

This domain modeling approach updates CONTEXT.md inline when terminology conflicts are resolved, and it optionally creates Architecture Decision Records using an explicit trade-off test when justified by the design review.

You should not use glossary conflict detection for codebase review when your design discussion lacks precise boundary definitions, as the relentless domain interviewing requires defined requirements, relationships, and decision points to function effectively.