brainstorminglisted

# Brainstorming Ideas Into Designs Help turn ideas into fully formed designs and specs through natural collaborative dialogue. Start by understanding the current project context, then ask questions one at a time to refine the idea. Once you understand what you're building, present the design and get user approval. <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. </HARD-GATE> <!-- nicopowers-grounded-design:start --> ## Grounded Decisions and Plain-Language Handoffs Ground decisions in the current repository, relevant documentation, and recent history before asking the user. Resolve discoverable facts yourself and keep factual gaps separate from choices that require human judgment. If `docs/learnings/README.md` exists, read the index first and open only the notes relevant to the current design. If the index is absent, do nothing; do not create it or scan the directory during brainstorming. Treat any new repository directory as a design decision. Ask the user before including it in a written specification or plan; do not postpone the choice until implementation. When the design contains real independent decisions, **REQUIRED SUB-SKILL:** Use `nicopowers:grilling`. Its numbered frontier rounds replace the one-question rule only for decisions that are simultaneously unblo