grill-with-docs

You can verify an architecture proposal by stress-testing it against your repository's documented domain language and ADR history to find terminology mismatches and boundary violations. This ensures your plan aligns with the established project context before implementation.

Checking a refactor plan against ADR records identifies conflicts with documented decisions. The process probes your design through stepwise interrogation, pushing updates to your decision traceability logs when newly clarified choices emerge during the review.

Aligning new design terminology requires branch-by-branch interrogation that forces convergence with constraints defined in your context files. It narrows uncertainty one question at a time until your proposal's language matches the documented domain model.

Yes, prompt-based review supports refactoring proposals by applying stepwise question refinement with dependency-aware follow-ups. This interrogates your design until key decisions are clarified and ensures all terminology aligns with your project documentation.

You need to stress-test plans against domain docs when proposing architectural changes, refactors, or new features that require consistent terminology and decision traceability. This prevents undocumented shifts in your domain boundaries and project language.