grill-with-docs

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.

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 one question at a time, waiting for feedback on each question before continuing.

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.

If a question can be answered by exploring the codebase, explore the codebase instead.

Domain awareness

During codebase exploration, also look for existing documentation:

During codebase exploration, also look for existing documentation:

File structure

Most repositories have a single context:

Most repos have a single context:

/
├── CONTEXT.md
├── docs/
│   └── adr/
│       ├── 0001-event-sourced-orders.md
│       └── 0002-postgres-for-write-model.md
└── src/

If the root directory contains CONTEXT-MAP.md, the repository has multiple contexts. The mapping points to the location of each context:

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 create them when there is content to write. If CONTEXT.md does not exist, create it when the first term is settled. If docs/adr/ does not exist, create it when the first ADR is needed.

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 terminology the user uses conflicts with the existing language in CONTEXT.md , point it out immediately. "Your glossary defines 'cancellation' as X, but you seem to mean Y—which is it?"

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 terminology, propose a precise canonical term. "You say 'account'—do you mean customer or user? They are different things."

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 discussing domain relationships, stress-test them with concrete scenarios. Design scenarios that probe edge cases, forcing the user to specify precisely the boundaries between concepts.

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 is consistent. If you find a contradiction, reveal it: "Your code cancels the entire order, but you just said partial cancellation is possible—which is correct?"

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 settled, update CONTEXT.mdimmediately. Do not batch—capture it as it happens. Use the format in CONTEXT-FORMAT.md .

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

Do not couple CONTEXT.md with implementation details. Include only terminology that is meaningful to domain experts.

Don't couple CONTEXT.md to implementation details. Only include terms that are meaningful to domain experts.

Offer ADRs sparingly

Only propose creating an ADR when all three of the following conditions are met:

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

1. Hard to reverse — the cost of changing your mind later is substantial

   The cost of changing your mind later is meaningful

2. Surprising without context — future readers will wonder "why did they do it this way?"

   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 chose one for a specific reason

   There were genuine alternatives and you picked one for specific reasons

If any one of the three conditions is missing, skip the ADR. Use the format in ADR-FORMAT.md .

If any of the three is missing, skip the ADR. Use the format in ADR-FORMAT.md.