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.
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
Most repositories 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:
/
├── CONTEXT-MAP.md
├── docs/
│ └── adr/ ← 系统级决策
├── src/
│ ├── ordering/
│ │ ├── CONTEXT.md
│ │ └── docs/adr/ ← 特定于上下文的决策
│ └── billing/
│ ├── CONTEXT.md
│ └── docs/adr/
Create files lazily—only when you have content to write. If CONTEXT.mddoes not exist, create it when the first term is resolved. If docs/adr/does not exist, create it when the first ADR is needed.
During the session
Challenge against the glossary
When the user uses a term that conflicts with existing language in CONTEXT.md , point it out immediately. "Your glossary defines 'cancellation' as X, but you seem to mean Y—which one is it?"
Sharpen vague language
When the user uses a vague or overloaded term, propose a precise canonical term. "You say 'account'—do you mean customer or user? These are different things."
Discuss concrete scenarios
When discussing domain relationships, stress-test with specific scenarios. Invent scenarios that probe edge cases, forcing the user to stay 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, expose it: "Your code cancels the entire order, but you just said partial cancellation is possible—which is correct?"
Update CONTEXT.md inline
When a term is resolved, update CONTEXT.mdimmediately. Don't batch them—capture them as they happen. Use the format in CONTEXT-FORMAT.md .
CONTEXT.md should have no implementation details at all. Don't treat CONTEXT.md as a spec, a scratchpad, or a repository for implementation decisions. It is only a glossary.
Offer ADRs sparingly
Only offer to create an ADR when all three of the following conditions are true:
- Hard to reverse—the cost of changing your mind later is meaningful
- Surprising without context—a future reader would wonder "why did they do it this way?"
- The result of a real trade-off—a genuine alternative existed, and you chose one for a specific reason
If any of the three conditions is missing, skip the ADR. Use the format in ADR-FORMAT.md .