design-discovery-ideationlisted

# Design Discovery Ideation > **Style:** Mode-B-lite. Divergent product/UI exploration before decisions lock; no production code. ## Purpose Help the Product Owner turn "show options" / "try approaches" requests into clear, bounded alternatives before implementation. The skill separates fixed constraints from open design dimensions, presents 2-4 meaningfully different directions, and feeds the chosen direction into `spec.md` or `decisions.md`. ## When to invoke - Operator asks for options, variations, alternatives, ideas, directions, or other possible shapes. - A UI, workflow, prompt, dashboard, or product behavior needs divergent exploration before lock. - `requirements-specification` finds unclear product framing or user experience scope. - `implementation-planning` needs real alternatives for a decision instead of a single recommendation. - Architect escalation is active and the design space spans multiple files, flows, or constraints. ## Do not invoke when - The task is a deterministic bug fix with known expected behavior. - A relevant decision is already LOCKED; AI Developer must implement or stop and surface a conflict. - Operator asks for direct implementation, not option discovery. - The only requested change is a narrow styling tweak with no product/design ambiguity. - Required context is unavailable and cannot be inspected read-only. ## Required inputs | Input | Where it lives | If missing | |---|---|---| | Operator intent | chat, backlog ticket, or `spec.m