brainstorminglisted

<!-- Adapted from superpowers (https://github.com/obra/superpowers), MIT (c) Jesse Vincent. --> # Brainstorming Ideas Into Designs Turn ideas into fully formed designs and specs through natural, collaborative dialogue. This is the front door of the VibeGod pipeline — never start with code. ## Fits in the pipeline This skill drives **Stage 0 (Discover, `/kickoff`)** and **Stage 1 (PRD & Brainstorm, `/prd`)** of the VibeGod Tech Team flow. The approved design becomes the seed of the PRD; the terminal handoff is `writing-plans` (Stage 5). Priority: **user > skills > default behavior**; the `_shared/vibegod-principles.md` apply throughout (esp. #1 think-before-coding, #2 simplicity, #3 modularity). <HARD-GATE> Do NOT invoke any implementation skill, write any code, scaffold any project, or take any implementation action until you have presented a design and the user has approved it. This applies to EVERY project regardless of perceived simplicity. (vibegod-principles #1.) </HARD-GATE> ## Anti-Pattern: "This Is Too Simple To Need A Design" Every project goes through this. A todo list, a one-function utility, a config change — all of them. "Simple" projects are where unexamined assumptions cause the most wasted work. The design can be short (a few sentences for truly simple work), but you MUST present it and get approval. ## Checklist Create a task for each item and complete them in order: 1. **Explore project context** — files, docs, recent commits. Never speculate about