Grilling session that challenges your plan against the project's documented domain language and decision records, sharpens terminology, and updates the glossary and ADRs inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
86%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.
Ask the questions one at a time, waiting for feedback on each question before continuing.
If a question can be answered by exploring the codebase, explore the codebase instead.
During codebase exploration, also read the project's own documentation. This kit
puts it in two places, both of them pointed at from the root AGENTS.md:
/
├── AGENTS.md ← the agent manual; points at both of these
├── docs/
│ ├── domain-glossary.md ← the ubiquitous language
│ ├── diary.md ← the chronology; "Current state" first
│ └── adr/
│ ├── INDEX.md ← what is currently binding
│ ├── NNNN-template.md ← copy this to start a new record
│ └── 0001-….md
└── constitution/ ← the layered rules the manual points atA repo with several bounded contexts may keep one glossary section (or one
glossary file) per context and let docs/domain-glossary.md be the index. Infer
which context the current topic belongs to; if it is not obvious, ask — an
ambiguous context is itself a finding.
If the project's layout differs, read AGENTS.md: the manual names where the
glossary and the decision records actually live, and it is the authority here,
not this file.
Create files lazily — only when you have something to write. If no glossary exists yet, create it when the first term is resolved. If no decision-record directory exists, create it when the first record is needed.
When the user uses a term that conflicts with the existing language in the glossary, call it out immediately. "Your glossary defines 'cancellation' as X, but you seem to mean Y — which is it?"
When the user uses vague or overloaded terms, propose a precise canonical term. "You're saying 'account' — do you mean the Customer or the User? Those are different things."
When domain relationships are being discussed, stress-test them with specific scenarios. Invent scenarios that probe edge cases and force the user to be precise about the boundaries between concepts.
When the user states how something works, check whether the code agrees. If you find a contradiction, surface it: "Your code cancels entire Orders, but you just said partial cancellation is possible — which is right?"
When a term is resolved, update the glossary right there. Don't batch these up — capture them as they happen. Use the format in GLOSSARY-FORMAT.md.
The glossary should be totally devoid of implementation details. Do not treat it as a spec, a scratch pad, or a repository for implementation decisions. It is a glossary and nothing else.
Only offer to create an ADR when all three are true:
If any of the three is missing, skip the ADR. Use the format in ADR-FORMAT.md.
Adapted from engineering/grill-with-docs in mattpocock/skills — MIT, see .claude/skills/LICENSE-mattpocock-skills.md. Upstream keeps the ubiquitous language in a root CONTEXT.md and proposes its own ADR template; both sidecars were rewritten to point at the artifacts this kit establishes.
agranado2k/google-books-clojure
76766c5
Also appears in
since Nov 19, 2026
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.