brainstorm-lean

# brainstorm-lean Turn an idea into a validated design through collaborative dialogue, then hand off to the implementation plan. No code is written here. No implementation skill runs until the user has approved a design. ## 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 in writing. **This applies to every project regardless of perceived simplicity.** A todo list, a single-function utility, a config change — all go through this gate. The design can be short (a few sentences for truly simple projects), but you MUST present it and get approval. ## When to invoke The first skill in the vibe pipeline. Invoke whenever the user asks to build, add, modify, or refactor a feature — no exceptions. ## Anti-pattern: "this is too simple to need a design" Every project goes through this process. "Simple" projects are where unexamined assumptions cause the most wasted work. ## Checklist Create a task for each item. Complete in order: 1. **Explore project context** — files, docs, recent commits. 2. **Ask clarifying questions** — one at a time; purpose, constraints, success criteria. 3. **Pushback turn** — before proposing approaches, challenge the framing if a simpler path exists. 4. **Propose 2-3 approaches** — with trade-offs and your recommendation. 5. **Present design** — in sections scaled to complexity; approval after each section. 6. **Wri...