grill-with-docs

You validate technical plans by initiating a structured grilling session that cross-references your proposed changes against existing CONTEXT.md glossaries and ADR history to ensure terminology consistency and design rigor.

You need an Architecture Decision Record when a structured validation interview determines your proposed design choice warrants formal documentation of trade-offs to prevent architectural drift and design ambiguity.

You prevent architectural drift by forcing your plans to align with your project's established domain language, challenging proposed changes against existing CONTEXT.md terminology to ensure consistency.

You check terminology alignment by cross-referencing your proposed changes against existing CONTEXT.md glossaries through iterative feedback loops that refine terminology and verify domain-driven design consistency.

The best way to ensure design consistency is to initiate a grilling session that reviews your proposed plan against the current domain model and validates terminology before implementation begins.