brainstorminglisted

# Brainstorming Use this skill to freeze direction before planning, spec writing, or code. This skill only serves the top-level or PM orchestration path. It exists to lock semantic ambiguity and design direction outside implementation, not to block routine small work or specialist execution. ## Trigger - Use when a MEDIUM/LARGE request in the top-level or PM planning gate still has route-changing ambiguity. - Use when 2 or more viable routes change implementation path, API behavior, data model, module ownership, UX direction, security boundary, or delivery scope. - Use when 3 or more candidate directions would materially change implementation and should be resolved through native structured selection. - Use when the request contains hotspot ambiguity such as `optimize`, `refactor`, `add feature`, `change this`, or `not allowed` and the default interpretation is not yet locked. - Use when a major new feature touches shared abstractions, external interfaces, or multi-module coordination and the direction is still open. Do not use when: - The task is small, isolated, and directionally clear. - A complete spec already exists and the direction has already been confirmed upstream. - The current flow is a direct specialist invocation rather than the top-level or PM planning gate. - There is only one reasonable interpretation and it can be recorded safely. ## Interview Mode 1. Ask one question at a time. Do not stack multiple branching questions in one turn. 2. Prefer 2-4 opt