grill-with-docslisted

# Grill With Docs ## Overview A relentless interview that treats every claim as unverified until a source is cited. Ordinary grilling sharpens what *you* think; this sharpens what is *true*, then writes it down. **Core principle:** an unsourced claim is an open question wearing a confident face. Two things distinguish this from `grilling` alone: 1. **Every claim under interview is checked against a source** — the documentation, the code, the spec, the API's real behaviour — before it is allowed to settle a branch of the design tree. 2. **The session produces artifacts**, not just agreement: decisions land as ADRs, vocabulary lands in the glossary. An interview that resolves five forks and records none of them did not happen. ## When to Use - A plan or design rests on claims about a library, API, protocol, or spec nobody has read end to end - "The docs say…" / "I think it works like…" / "it should support…" — assertion without citation - A requirements interview over a heavy document or spec corpus - Onboarding a domain where the vocabulary is not yet pinned down - Before committing to an integration whose real behaviour is assumed rather than established **Not for:** eliciting *preferences* (use `grilling` — there is no source to check a preference against); exploring intent from scratch (use `brainstorming`); a decision with scorable criteria and no factual dispute (use `decision-matrix`). ## Step 0: Assert the dependencies loaded — do this first, every time