grill-with-docs

To validate an architecture plan against existing documentation, interrogate your design assumptions step-by-step against your domain glossary to ensure terminology consistency and capture trade-offs in ADRs.

You should write an ADR when a design change reflects a hard-to-reverse trade-off, is surprising without context, and represents a real alternative among documented architectural decisions.

Keep a domain glossary consistent during integration planning by challenging conflicting or vague terms during design interrogation and applying controlled updates to your CONTEXT.md file as terms are resolved.

The best way to stress-test a design before implementation is conducting incremental, one-question-at-a-time exploration that cross-references your codebase and existing documentation to align assumptions.

Architecture review requires an existing or planned CONTEXT.md file because the process validates terminology alignment and applies controlled updates directly to the domain glossary documented there.

Terminology alignment fails during codebase inspection when a proposed design introduces conflicting or vague terms that diverge from the documented domain glossary and existing architectural decisions.