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. ## Size Gate — assess first, before engaging further **Size gate:** trivial → skip (no artifact); medium → lean plan only (no separate spec); large/ambiguous → full spec. The trigger is **ambiguity/complexity, not size alone** — a small change that hinges on a load-bearing decision still gets the full treatment below; a large but mechanical change doesn't. - **Trivial** (no real ambiguity, no decision to make) → skip this skill entirely. No spec, no plan — just do it. - **Medium** (some judgment calls, but scoped and clear) → skip the separate spec. Go straight to a lean plan via the writing-plans skill, with a 2-3 line "why" header at the top of the plan capturing the goal and key trade-off. No design doc. - **Large / ambiguous / load-bearing** → run the full process below: spec (durable why) → plan (disposable how, via writing-plans). When unsure which tier applies, size up rather than down — an unnecessary question costs one exchange; a missed decision costs rework. <HARD-GATE> For large/ambiguous work (see Size Gate above), do NOT invoke any implementation skill, write any code, scaffold any project, or take any implementation action until you have prese