refine-idealisted

# Refine Idea Use this skill when the user has a rough idea, feature thought, transcript, pain point, opportunity, or solution proposal and wants help deciding what the idea actually is and whether it is worth pursuing. This skill is deliberately **before requirements discovery**. Do not turn the idea directly into implementation tickets unless the user explicitly asks to skip discovery and the idea is already decision-complete. ## Goal Produce a concise **Refined Idea Brief** that answers: - What problem are we solving? - Who has the problem? - Why does it matter? - What outcome would make the idea valuable? - What assumptions are we making? - What alternatives exist? - What is the smallest useful version? - What is intentionally not part of the idea? - What material unknowns still need requirements discovery, research, design, or technical validation? The agent is expected to challenge the premise. A valid outcome is **do not build**, **defer**, **combine with existing capability**, or **run discovery first**. ## Conversational discovery Do not dump a questionnaire on the user. Progressively resolve the highest-value uncertainty first. Prefer one focused question at a time when user input is needed. Use existing repository, architecture, GitHub issues, and conversation context before asking questions the answer may already contain. Typical sequence: 1. Restate the idea in one sentence. 2. Identify the user/problem, not just the proposed solution. 3. Clarify desir