project-brainstorming

## When To Use - Starting a new project without clear requirements - Exploring problem space before specification - Need to compare multiple approaches systematically - Validating project feasibility and scope - Documenting decision rationale for stakeholders - Need to clarify the core problem being solved ## When NOT To Use - Requirements and specification already exist (use `Skill(attune:project-planning)` instead) - Refining existing specs (use `Skill(attune:project-specification)` instead) - Project scope is well-defined (jump to `/attune:project-init`) - Mid-project pivots (use `Skill(attune:war-room)` for strategic decisions) ## Integration **With superpowers**: - Delegates to `Skill(superpowers:brainstorming)` for Socratic method - Augments with project-specific patterns - Uses project brainstorm templates **Without superpowers**: - Standalone questioning framework - Project-focused ideation patterns - Structured output templates **War Room Integration (REQUIRED)**: - After Phase 3 (Approach Generation), automatically invokes `Skill(attune:war-room)` - All brainstorming context passed to War Room for expert deliberation - War Room provides multi-LLM pressure testing and synthesis - Only bypassed for Type 2 decisions (RS ≤ 0.40) with explicit user confirmation ## Brainstorming Framework ### Phase 1: Problem Definition **Socratic Questions**: 1. What problem are you solving? 2. Who experiences this problem? 3. What makes this problem worth solving now? 4. What ...