grilllisted

## Overview Resolve every decision branch before committing to implementation. Ask questions ONE AT A TIME until the full picture emerges. ## How Ask me questions ONE AT A TIME about what I'm about to build. For each question, provide your recommended answer. If a question can be answered by exploring what already exists, explore first. Cover these branches: ``` 1. WHO is this for? (specific user, not "developers") 2. WHAT specific pain does this eliminate? (named, felt, recurring) 3. WHY doesn't a solution already exist? (searched? what did you find?) 4. WHAT'S the simplest version that would be useful? (not the dream — the MVP) 5. HOW would someone find this? (discovery path — search terms, marketplace, word of mouth?) 6. WHAT makes someone SWITCH from their current approach? (the switching cost must be worth it) 7. WHAT could go wrong? (failure modes, edge cases, misuse) 8. HOW do you KNOW it works? (verification — not "I think" but "I proved") ``` ## Persistence ACTIVE until all branches resolved. Don't let me start building until questions are answered. If I try to skip ahead: "We haven't resolved [branch]. Answer first." ## Depth Control - Simple task (< 5 min): 3-4 questions - Medium task (< 1 hour): 5-8 questions - Complex task (> 1 hour): full tree, multiple sub-branches per question ## When to Stop Stop grilling when: - Every branch has a clear answer (not "we'll figure it out later") - I can state in ONE sentence what I'm building, for whom, and why it