grill-with-docs

name	grill-with-docs
description	Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (product/glossary.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.

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.

Domain awareness

During codebase exploration, also look for existing documentation:

File structure

Bowties uses a single glossary and ADR directory:

/
├── product/
│   ├── glossary.md                   ← domain vocabulary
│   └── architecture/
│       └── adr/                      ← architecture decision records
│           └── README.md
└── aiwiki/                           ← code-level navigation for AI

The glossary and ADR directory already exist. Update them inline as terms and decisions crystallize during the session.

During the session

Challenge against the glossary

When the user uses a term that conflicts with the existing language in product/glossary.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 product/glossary.md inline

When a term is resolved, update product/glossary.md right there. Don't batch these up — capture them as they happen. Use the format in GLOSSARY-FORMAT.md.

Don't couple the glossary to implementation details. Only include terms that are meaningful to domain experts or that prevent ambiguity for AI agents.

Offer ADRs sparingly

Only offer to create an ADR when all three are true:

1. Hard to reverse — the cost of changing your mind later is meaningful
2. Surprising without context — a future reader will wonder "why did they do it this way?"
3. 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 ADR-FORMAT.md.