grill-with-docslisted

A relentless grilling session that ALSO builds the project's shared language as you go — runs the /grill interview while /domain-model captures crystallizing terms into CONTEXT.md and decisions into ADRs, inline. You leave aligned AND with the glossary/decisions written down, so the next session is terser and the codebase gets named consistently. TRIGGER when: the user wants to stress-test a design AND pin down its terminology/decisions — "grill me and document it", "grill with docs", aligning on something worth recording. DO NOT TRIGGER when: a quick plain stress-test is enough (use /grill), or it's pure glossary/ADR work with no plan to interrogate (use /domain-model).
mik2win/foureyes · ★ 2 · AI & Automation · score 79

Install: claude install-skill mik2win/foureyes

# Grill With Docs: $ARGUMENTS Run a **`/grill`** session and a **`/domain-model`** session at the same time. The grilling drives alignment; the domain-modeling captures the language and decisions the grilling surfaces — written down the *moment* they crystallize, not in a "document it later" step that never happens. This is arguably the highest-leverage technique in the kit: a single interview that aligns you with the agent **and** builds a shared vocabulary. The payoff compounds — variables, functions, and files get named from the same language; the codebase becomes easier to navigate; the agent spends fewer tokens because one precise term replaces a paragraph of explanation. `$ARGUMENTS` is the plan or design to grill. If empty, ask what to grill, then stop. --- ## How it runs This skill **composes the two primitives** — it adds no new interview or glossary mechanics of its own. Drive both in lockstep: 1. **Ground** — load `.claude/PROJECT.md` (Domain, Architecture) and `CONTEXT.md` + `docs/adr/` if present, per each primitive's Phase 0. The glossary you read is also the one you'll extend. **Profile optional.** Like both primitives, this runs with or without a profile: if `.claude/PROJECT.md` is missing or still `TEMPLATE`, proceed on the plain subject (lean on the root `CLAUDE.md` if it carries the facts) and tell the user `/bootstrap` will wire the `CONTEXT.md` / `docs/adr/` locations into it. 2. **Grill** — run the **`/grill`** loop on `$ARGUMENTS`: