By name: grill-with-docs
description: Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions. Pass --light for a faster pass with no counter-challenges.
Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the decision tree, resolving both top-level decisions and the sub-decisions they unlock. For each question, provide your recommended answer.
Ask one question at a time. You may bundle 2 (rarely 3) sub-decisions into one turn only when they're all parameters of the same choice you just made, such that asking separately would require restating the same setup. If the bundle would require more than a short paragraph of setup plus brief options, split it. Err on the side of splitting.
If a question can be answered by exploring the codebase, explore instead of asking. Keep exploring mid-interview whenever an answer surfaces a new constraint that reshapes later branches.
When I answer directly — not by picking from a menu you offered — push back once before accepting ("Did you consider X?", "What breaks if Y?"). One probe, then move on. Skip the challenge if I picked from your menu, or if I pass --light.
Stop condition
Stop when every branch and its unlocked sub-decisions have a decision or an explicit open question. Produce a wrap-up with three sections: Decisions made (with brief rationale), Assumptions accepted (each with a one-line justification), Open questions still requiring resolution.
Honesty rule: Any default I did not explicitly confirm belongs under "assumptions" or "open questions," never silently in "decisions." If assumptions exceed ~3 items, you missed questions — go back and ask.
NEVER
- NEVER accept "I'll figure that out later" — require a decision or mark it as an open question.
- NEVER ask multiple top-level questions in one turn (bundling coupled sub-decisions within one branch is fine).
- NEVER stop at surface-level branches — drill into sub-decisions as they emerge from answers.
- NEVER silently default on something I didn't confirm.
Domain awareness
During codebase exploration, also look for existing documentation:
File structure
Most repos have a single context:
/
├── CONTEXT.md
├── docs/
│ └── adr/
│ ├── 0001-event-sourced-orders.md
│ └── 0002-postgres-for-write-model.md
└── src/
If a CONTEXT-MAP.md exists at the root, the repo has multiple contexts. The map points to where each one lives:
/
├── CONTEXT-MAP.md
├── docs/
│ └── adr/ ← system-wide decisions
├── src/
│ ├── ordering/
│ │ ├── CONTEXT.md
│ │ └── docs/adr/ ← context-specific decisions
│ └── billing/
│ ├── CONTEXT.md
│ └── docs/adr/
Create files lazily — only when you have something to write. If no CONTEXT.md exists, create one when the first term is resolved. If no docs/adr/ exists, create it when the first ADR is needed.
During the session
Challenge against the glossary
When the user uses a term that conflicts with the existing language in CONTEXT.md, call it out immediately. "Your glossary defines 'cancellation' as X, but you seem to mean Y — which is it?"
Sharpen fuzzy language
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."
Discuss concrete scenarios
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.
Cross-reference with code
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?"
Update CONTEXT.md inline
When a term is resolved, update CONTEXT.md right there. Don't batch these up — capture them as they happen. Use the format in references/CONTEXT-FORMAT.md.
CONTEXT.md should be totally devoid of implementation details. Do not treat CONTEXT.md as a spec, a scratch pad, or a repository for implementation decisions. It is a glossary and nothing else.
Offer ADRs sparingly
Only offer to create an ADR when all three are true:
- Hard to reverse — the cost of changing your mind later is meaningful
- Surprising without context — a future reader will wonder "why did they do it this way?"
- The result of a real trade-off — there were genuine alternatives and you picked one for specific reasons
If any of the three is missing, skip the ADR. Use the format in references/ADR-FORMAT.md.