grillme

You validate a design plan by running a Socratic, one-question-at-a-time interview against the repository's domain glossary and ADR history, surfacing terminology drift, hidden assumptions, and missing decisions prior to implementation.

A Socratic review is an interactive questioning process that probes a tactical or architectural design proposal one question at a time, checking it for consistency against documented domain truth and prior architecture decisions to prevent costly misunderstandings.

You check for conflicts by scoping the review to a bounded context via CONTEXT-MAP.md and probing the existing CONTEXT.md and docs/adr/ directory, asking targeted questions to identify missing decisions or terminology drift in the proposed plan.

Yes, you can use a --no-write dry-run mode to emit proposed patch updates to CONTEXT.md without applying them, as all constrained file writing is gated behind explicit per-write confirmation for safe read-only probing.

You should create a new ADR when the plan validation surfaces a decision that is hard to reverse, surprising without context, and reflects a real trade-off with rejected alternatives, ensuring the architectural choice is properly documented.

Validation is limited by the read-only probing of existing CONTEXT.md, CONTEXT-MAP.md, and docs/adr/ files, meaning it cannot validate plans effectively if the repository lacks prior domain documentation or established architectural decision records.