brainstorminglisted
Install: claude install-skill seyio91/ai-memory-system
# Brainstorming Features Into Designs
Turn a rough feature idea into an approved design through collaborative dialogue, then hand the design to `/new-plan` so the existing orchestrator/executor pipeline can run it.
This is the **front half** of the Tier-3 pipeline. It sits *before* `/new-plan` and produces its inputs. It does not write code, scaffold anything, or create the plan file itself — its only output is an approved design that gets folded into the plan.
## When this fires — and when it doesn't
This skill is gated to one slice of work: **Tier-3 feature tasks with open design questions.** The tier classification that already runs on every request is the gate.
| Request | Tier | Brainstorm? |
|---------|------|-------------|
| "what does X do", "how should we approach Y" | 1 — research/Q&A | No — answer directly |
| one edit, a one-off command, a short fix | 2 — quick item | No — just do it |
| new feature / subsystem / integration with design choices to make | 3 — feature | **Yes** |
| multi-file refactor, rename, migration with a known shape | 3 — settled | No — go straight to `/new-plan` |
The distinction inside Tier 3 is **open design questions vs. settled shape.** If you already know exactly what files change and how, there is nothing to brainstorm — scaffold the plan. If there are real choices (data model, interface boundaries, where a responsibility lives, how pieces talk), brainstorm first.
If you started executing and realize the design is not actually se