grill-me

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.

Use related skills during the grilling session when their trigger conditions appear:

• Use ubiquitous-language when terms are vague, overloaded, conflicting, or important enough to become shared domain language. Read and update GLOSSARY.md using the rules in ../ubiquitous-language/SKILL.md.
• Use architecture-decision-record when a decision is hard to reverse, surprising without context, and the result of a real trade-off. Record ADRs using ../architecture-decision-record/templates/adr-template.md.

Do not duplicate those workflows inside this skill. Delegate glossary wording and ADR formatting to the related skill instructions, then return to the grilling sequence.

Domain awareness

During codebase exploration, also look for existing documentation:

File structure

Most repos have a single context:

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

Create files lazily — only when you have something to write. If no GLOSSARY.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 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."