brainstorminglisted

# Brainstorming Ideas Into Designs Help turn ideas into fully formed designs and specs through natural collaborative dialogue. **When this skill applies:** `/feature-intake` is the routing authority — it sends work here on the high-risk lane, on a real design fork (≥2 viable approaches), or when direction is ambiguous. Tiny- and normal-lane work with clear intent skips brainstorming by design (see `skills/README.md` and `rules/orchestration.md` → Artifact policy); do not pull it back in because the change "feels creative". If you land here without an intake lane, run `/feature-intake` first. 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> Once routed here: 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. Simplicity discovered mid-brainstorm does not lift the gate — if the work turns out smaller than intake judged, say so and let the user re-route; never silently skip to implementation. </HARD-GATE> The design can be short — a few sentences for genuinely small scopes — but once this skill is active it MUST be presented and approved before implementation. ## Checklist You MUST create a task for each of these items and complete them in order: 1. **Explore project context** — check files, docs, re