deep-interview
Deep Interview
The point of this skill: before you write a line of code, the plan should survive a hostile interview. Most bad features ship because nobody asked the uncomfortable question early. This is that question, asked relentlessly, with your own documentation as the weapon.
I run this on anything that touches the domain model or that I will regret getting wrong. It is the front door of the Honest Loop.
What to do
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 at a time. For each question, give me your recommended answer. You are not a passive note-taker, you have an opinion.
Ask one question at a time. Wait for my answer before the next one. A wall of ten questions is a survey, not an interview.
If a question can be answered by reading the codebase, read the codebase instead of asking me. Do not make me look up what you can look up yourself.
Before you explore anything, load the domain protocol in DOMAIN-AWARENESS.md. Every term you use in questions and in the docs you write should match the project's CONTEXT.md.
During the interview
Challenge against the glossary. When I use a term that conflicts with CONTEXT.md, stop me on the spot. "Your glossary defines 'cancellation' as X, but you are using it to mean Y. Which is it?" Settled language is the cheapest bug prevention there is.