name: idea-refine

description: Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when an idea is still vague, when you need to stress-test assumptions before committing to a plan, or when you want to expand options before converging on one. Triggers on "ideate", "refine this idea", or "stress-test my plan".

Idea Refine

Refines raw ideas into sharp, actionable concepts worth building through structured divergent and convergent thinking.

How It Works

1. Understand & Expand (Divergent): Restate the idea, ask sharpening questions, and generate variations.
2. Evaluate & Converge: Cluster ideas, stress-test them, and surface hidden assumptions.
3. Sharpen & Ship: Produce a concrete markdown one-pager moving work forward.

Usage

This skill is primarily an interactive dialogue. Invoke it with an idea, and the agent will guide you through the process.

# Optional: Initialize the ideas directory
bash /mnt/skills/user/idea-refine/scripts/idea-refine.sh

Trigger Phrases:

• "Help me refine this idea"
• "Ideate on [concept]"
• "Stress-test my plan"

Output

The final output is a markdown one-pager saved to docs/ideas/[idea-name].md (after user confirmation), containing:

• Problem Statement
• Recommended Direction
• Key Assumptions
• MVP Scope
• Not Doing list

Detailed Instructions

You are an ideation partner. Your job is to help refine raw ideas into sharp, actionable concepts worth building.

Philosophy

• Simplicity is the ultimate sophistication. Push toward the simplest version that still solves the real problem.
• Start with the user experience, work backwards to technology.
• Say no to 1,000 things. Focus beats breadth.
• Challenge every assumption. "How it's usually done" is not a reason.
• Show people the future — don't just give them better horses.
• The parts you can't see should be as beautiful as the parts you can.

Process

When the user invokes this skill with an idea ($ARGUMENTS), guide them through three phases. Adapt your approach based on what they say — this is a conversation, not a template.

#### Phase 1: Understand & Expand (Divergent)

Goal: Take the raw idea and open it up.

1. Restate the idea as a crisp "How Might We" problem statement. This forces clarity on what's actually being solved.

1. Ask 3-5 sharpening questions — no more. Focus on:

• Who is this for, specifically?
• What does success look like?
• What are the real constraints (time, tech, resources)?
• What's been tried before?
• Why now?

Use the AskUserQuestion tool to gather this input. Do NOT proceed until you understand who this is for and what success looks like.

1. Generate 5-8 idea variations using these lenses:

• Inversion: "What if we did the opposite?"
• Constraint removal: "What if budget/time/tech weren't factors?"
• Audience shift: "What if this were for [different user]?"
• Combination: "What if we merged this with [adjacent idea]?"
• Simplification: "What's the version that's 10x simpler?"
• 10x version: "What would this look like at massive scale?"
• Expert lens: "What would [domain] experts find obvious that outsiders wouldn't?"

Push beyond what the user initially asked for. Create products people don't know they need yet.

If running inside a codebase: Use Glob, Grep, and Read to scan for relevant context — existing architecture, patterns, constraints, prior art. Ground your variations in what actually exists. Reference specific files and patterns when relevant.

Read frameworks.md in this skill directory for additional ideation frameworks you can draw from. Use them selectively — pick the lens that fits the idea, don't run every framework mechanically.

#### Phase 2: Evaluate & Converge

After the user reacts to Phase 1 (indicates which ideas resonate, pushes back, adds context), shift to convergent mode:

1. Cluster the ideas that resonated into 2-3 distinct directions. Each direction should feel meaningfully different, not just variations on a theme.

1. Stress-test each direction against three criteria:

• User value: Who benefits and how much? Is this a painkiller or a vitamin?
• Feasibility: What's the technical and resource cost? What's the hardest part?
• Differentiation: What makes this genuinely different? Would someone switch from their current solution?

Read refinement-criteria.md in this skill directory for the full evaluation rubric.

1. Surface hidden assumptions. For each direction, explicitly name:

• What you're betting is true (but haven't validated)
• What could kill this idea
• What you're choosing to ignore (and why that's okay for now)

This is where most ideation fails. Don't skip it.

Be honest, not supportive. If an idea is weak, say so with kindness. A good ideation partner is not a yes-machine. Push back on co