Verdict
Grill With Docs improves on a normal requirements interview by turning resolved language and architectural choices into durable project context. That makes later sessions shorter and reduces inconsistent naming across both code and agent explanations.
Best for
Long-lived codebases where domain vocabulary, ADRs, and session-to-session continuity matter as much as the immediate feature.
Keep in mind
It can produce documentation overhead when the domain is simple, and teams must maintain the resulting context files or their authority decays.
Example task
Interrogate the billing-domain redesign and update our glossary and ADRs as each product and data-model decision becomes stable.