oracle-grillmelisted

# Grill Me Relentless questioning of your plan against the project's domain model, sharpening terminology and updating documentation (CONTEXT.md, ADRs) inline as decisions crystallise. ## When to Use - **Stress-testing a plan** — "I want to add a refund flow to the Order service" - **Clarifying fuzzy language** — "We're calling it 'account' but is that a Customer or a User?" - **Onboarding to a domain** — "Walk me through how the Billing context relates to Ordering" - **Before writing specs** — Ensuring the domain language is solid before `spec-research` begins - **After code review** — "The PR introduces 'cancellation' but our glossary says..." ## When NOT to Use - **Simple implementation questions** — Use `oracle-challenge` or `oracle-architect` instead - **Debugging** — Use `code-debug` - **Testing strategy** — Use `oracle-testing` - **Already in spec workflow** — Use `spec-research` + `oracle-architect` for domain discovery during the spec process --- ## How It Works <interview-loop> 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. </interview-loop> --- ## Domain Awareness ### Discovering Con