grill-with-docs

Validate domain terminology by challenging a proposed design plan against an existing domain glossary and documented decisions to eliminate mismatched terms and unclear boundaries. The process cross-checks assumptions with the codebase and docs to ensure accurate terminology alignment.

Align architecture review terminology by applying relentless domain questioning to interview every assumption and force precise answers about terms and boundaries. This detects conflicts with your documented language and resolves ambiguous terms into canonical glossary entries.

Create an ADR during a refactoring discussion only when a resolved decision has real trade-offs that are hard to reverse. The process uses sparing ADR creation criteria and formats, prioritizing inline CONTEXT.md updates for standard terminology resolutions instead.

Update CONTEXT.md through immediate inline updates as ambiguous terms get resolved during the questioning process. This ensures that canonical glossary entries are captured directly in the documentation while the design plan is being stress-tested.

Yes, you can use domain questioning to stress-test product and system design plans before implementation by challenging them against existing domain language. This ensures terms and relationships align with the codebase and docs, preventing mismatched terminology.

Terminology alignment requires one-at-a-time questioning with codebase cross-checks to accurately resolve each term and boundary. This methodical approach ensures precise answers and immediate CONTEXT.md inline updates without missing contextual dependencies.