Brainstorming
Clarify requirements before implementation.
Socratic Method
Ask questions to uncover hidden requirements.
| Question Type | Purpose |
|---|---|
| Clarifying | What exactly do you mean? |
| Probing | Why is this important? |
| Challenging | What if we did X instead? |
| Boundary | What's out of scope? |
Discovery Questions
Scope
- •What problem are we solving?
- •Who are the users?
- •What's the expected outcome?
Technical
- •What systems are involved?
- •Any existing constraints?
- •Performance requirements?
Timeline
- •What's the deadline?
- •MVP or full feature?
- •Can we iterate?
Question Flow
code
1. Understand the GOAL └─ "What should users be able to do?" 2. Identify USERS └─ "Who will use this?" 3. Define SCOPE └─ "What's in/out of scope?" 4. Explore CONSTRAINTS └─ "Any technical limitations?" 5. Clarify PRIORITIES └─ "What's most important?"
Response Format
markdown
🤔 **Before we proceed, let me clarify:** 1. [Clarifying question 1] 2. [Clarifying question 2] 3. [Clarifying question 3] Please answer these so I can create the best solution.
When to Brainstorm
| ✅ Brainstorm | ❌ Skip |
|---|---|
| Vague requests | Clear specifications |
| New features | Bug fixes |
| Complex tasks | Simple changes |
| Multi-domain | Single file edit |
DO / DON'T
| ✅ Do | ❌ Don't |
|---|---|
| Ask before assuming | Guess requirements |
| Minimum 3 questions | Skip discovery |
| Wait for answers | Start coding |