grill-with-docs

You pressure-test a plan by cross-checking it against existing domain documentation like CONTEXT.md files and ADRs to catch terminology contradictions and hidden trade-offs before implementation begins.

Aligning design decisions with a codebase glossary involves structured interviewing that detects terminology conflicts and updates context files inline as terms are resolved during the design discussion.

Create an ADR during a design review when a decision is hard to reverse, surprising to the team, and driven by meaningful trade-offs that warrant permanent architectural documentation.

Yes, you can update CONTEXT.md files during planning by resolving domain terminology conflicts through one-at-a-time questioning, which lazily creates or modifies context files only when justified.

Yes, this approach works for repository walkthroughs by applying controlled questioning against documented domain language and performing live documentation updates as decisions are finalized.