user-brainstormlisted

# user-brainstorm Help the user explore and document an arbitrary topic — engineering pattern, architectural concern, product question, design space — by producing a tiered reference set. The activity has two phases: **interactive ideation** (seed → gap-fill → tier, with the user in the loop) and **parallel investigation** (one background sub-agent per topic writes a templated reference file). The output is a self-contained, navigable doc set the user can grep later. ## When to use - User wants to ideate comprehensively on a topic. - User asks "what are the considerations for X" or similar open-ended exploration. - User wants a reference doc set produced from a back-and-forth, not a one-shot answer. - After running, the user has a folder of cross-referenced investigations they can refer back to. ## When NOT to use - Single specific question with a single specific answer — just answer it. - Topic is already covered by an existing doc set — point at that instead. - Topic is too narrow (one concern, not a space of concerns). ## Steps ### 1. Get the topic Required argument. If not provided, ask: "What topic do you want to brainstorm?" Derive a kebab-case slug from the topic. Confirm the output path with the user (default: `docs/investigations/<slug>/` relative to CWD). ### 2. Seed 10 topics Generate **exactly 10** topics related to the subject. Each is a short noun phrase (3-8 words) describing a concern, pattern, failure mode, or design decision. Output as a numbered