grill-with-docslisted

# Grill With Docs `/grill-me` with the spec loaded. The interview rules are the same (research first, one question at a time, always recommend, order by dependency, respect diverged answers, flag assumptions — see the `grill-me` skill); what changes is that the project's recorded domain model sits on the table, and the session **writes back to it as it goes**. ## Setup Read `[tool.patdhlk-skills]` from `ubproject.toml`; the `term` and `decision` roles must be mapped (missing → `/setup-patdhlk-skills`). Build a fresh needs.json (ADR_0006) and load: - all **terms** — the project's vocabulary, - all **decisions** with status and links, - the **features/requirements** the plan touches. Glossary location: `terms_doc` from the config when set; otherwise find where term directives live, ask once, persist as `terms_doc`. Decisions go to `decisions_doc` (same mechanism, shared with `/decide`). ## The three doc-grounded behaviors Layered on top of the normal grilling: 1. **Challenge with the record.** When the plan touches ground covered by an accepted decision, quote it by ID: "ADR_0006 says reads go through needs.json — your plan greps RST. Change the plan, or supersede the decision?" A plan is never allowed to silently contradict the record: the contradiction is resolved in-session, one way or the other. 2. **Sharpen terminology.** When the user's words drift from a recorded term, hold up the glossary definition and ask which is right. When the session coi