← ClaudeAtlas

brainstorminglisted

Use before starting a large, non-trivial feature task (a Tier-3 task in this system) that still has open design questions — new functionality, a new subsystem, a new integration, or a real architecture decision. Refines the idea through collaborative dialogue, settles on an approach, and produces an approved design that is folded directly into a plan file via /new-plan. Invoke this whenever a feature is big enough to warrant a plan AND its shape is not already obvious — including when a /start command begins a captured feature task. Do NOT use for research/explore/Q&A (Tier 1), quick one-off edits or fixes (Tier 2), or Tier-3 work whose design is already settled (mechanical refactors, renames, migrations with a known target). When in doubt on a feature-sized task, invoke it — a short design is cheap; an unexamined assumption is not.
seyio91/ai-memory-system · ★ 0 · AI & Automation · score 73
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