grill-melisted

# grill-me Interview the user about a plan or design until the key decisions needed to implement the current scope are resolved. ## How to run it - Read the plan, linked docs, code, or local files needed to understand the topic first. - Ask **one** question at a time. Wait for the answer before the next question. - For each question, state **your recommended answer** and a one-line why. - Follow branches that affect implementation of the current scope; record optional or out-of-scope branches for later. Resolve dependencies between key decisions in order. - If a question can be answered by **exploring the codebase**, explore instead of asking. - Push on fuzzy words, hidden assumptions, edge cases, dependencies between decisions, and reversibility. - Stop when the key implementation decisions are resolved. Summarize the agreed plan and record remaining non-blocking questions as follow-ups. ## Question patterns - "What outcome would make this change a success?" - "Which existing concept owns this behavior?" - "What is the smallest scenario that proves the design works?" - "What breaks if this assumption is false?" - "What would a future maintainer be tempted to change back?" - "Which term should be canonical, and which aliases should be avoided?" ## Capturing decisions Only when the repo already keeps `CONTEXT.md`, `CONTEXT-MAP.md`, or `docs/adr/`, or the interview resolves terminology or a decision worth outliving the conversation. Check for those files before proposing