pm-brainstormlisted

# Interactive Feature Brainstorming Guide the user from a rough idea to well-formed feature requests through conversation, research, and codebase understanding. Unlike `/pm-explore` (which autonomously generates suggestions) or `/pm-plan` (which takes a clear description and creates entities), this skill is for the messy early stage — when the user knows something could be better but hasn't crystallized what "better" looks like yet. The core loop: **Ask → Research → Ground → Refine → Create**. ## Step 0: Parse Arguments and Set Context Parse `$ARGUMENTS` for the brainstorming topic. This might be: - A specific area: "dashboard UX", "notifications", "reporting" - A problem statement: "it's hard to track progress across work packages" - A user segment: "features for new users", "admin workflows" - A vague direction: "what's missing?", "how can we improve things?" - Empty (no arguments) — that's fine, you'll discover the topic in Step 1 ## Step 1: Open the Conversation Start with a warm, exploratory question. The goal is to understand the user's mental model — what they care about, what's frustrating them, what opportunity they see. Don't jump to solutions yet. **If arguments were provided**, acknowledge the topic and ask a focusing question: Use `AskUserQuestion`: - Question: Based on the topic, ask something that narrows scope without closing off possibilities. Examples: - For "dashboard UX": "What's the most frustrating part of using the dashboard right now —