grill-with-docs

Validate an architecture plan by stress-testing its assumptions against documented decisions and domain models, interrogating terminology conflicts one question at a time to ensure shared understanding and alignment with established language.

Reconcile fuzzy domain terminology with CONTEXT.md by calling out overloaded terms during plan interrogation, proposing precise canonical definitions, and writing inline updates directly into the documentation as terms are resolved.

Cross-check an AI-generated plan by exploring the codebase to inspect existing dependencies and domain logic, immediately reconciling any contradictions found between the proposed plan and the actual implementation.

Ensure decisions align with existing ADRs by interrogating the proposed plan against documented architecture decisions, breaking down the design tree through gated questioning until terminology and logic match established records.

Plan validation mandates codebase exploration when relevant answers exist in code, ensuring the proposed software design is checked against actual dependencies and implementation logic rather than unverified assumptions.

Avoid domain model interrogation when a project lacks established CONTEXT.md or ADRs, as this approach relies on stress-testing plans against existing documented decisions and reconciling terminology with a mature domain glossary.