brainstorming

# Brainstorming > From [obra/superpowers](https://github.com/obra/superpowers) ## Purpose Turn rough ideas into fully-formed designs through collaborative dialogue, NOT immediate implementation. **Use for:** Exploring ideas, designing features, architecture decisions **NOT for:** Clear mechanical processes with obvious implementation ## The Three Phases ### Phase 1: Understanding the Idea 1. **Review existing context** - Read relevant project files - Understand current architecture - Note constraints and requirements 2. **Ask clarifying questions** - ONE question at a time - Prefer multiple choice when possible - Open-ended questions are fine too - Wait for answer before next question ``` Good: "Should this feature support offline mode? A) Yes, full offline support B) Yes, limited offline (read-only) C) No, online only" Bad: "What about offline support? And caching? Also, how should errors be handled?" ``` ### Phase 2: Exploring Approaches 1. **Present 2-3 different solutions** - Each with clear trade-offs - Lead with recommended option - Explain reasoning ```markdown ## Approach A: Event-Driven (Recommended) - Pros: Decoupled, scalable, easy to extend - Cons: More complex debugging, eventual consistency - Best for: Systems needing flexibility ## Approach B: Direct Integration - Pros: Simple, immediate consistency - Cons: Tight coupling, harder to scale - Best for: Small, stable systems ## Approach C: Hyb...