grill-with-docs

Stress-testing a plan against a domain model uses interview-driven questioning to walk the design tree and resolve decision dependencies one-by-one. It clarifies terminology and cross-references the codebase to reduce uncertainty before finalizing choices.

Updating CONTEXT.md and ADRs inline happens automatically during the review when confirmed decisions meet the ADR criteria for trade-offs. The documentation is updated directly as terminology conflicts are resolved and decisions crystallize through the questioning process.

Glossary conflict detection is handled by terminology-aware questioning that checks proposed plans against existing domain model language in CONTEXT.md. It resolves inconsistencies by aligning definitions one question at a time before capturing the agreed-upon terms.

Resuming a design review session is fully supported through session continuation, which recovers the prior grill state and the existing decision index. This allows you to continue incremental decision recovery without losing your previous progress or context.

Plan validation works without existing ADRs by focusing on CONTEXT.md domain models and codebase inspection. However, inline ADR updates only occur when the resolved trade-offs specifically meet the established ADR criteria during the grilling process.

One-question-at-a-time interaction with feedback gating ensures thorough architecture tradeoff analysis by forcing rigorous, sequential resolution of decision dependencies. This prevents speculative answers by prioritizing codebase inspection when questions can be answered by exploring the code.