idea-refine

Refine vague product concepts into actionable directions with structured ideation.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/ToanPV90/dotfiles --skill idea-refine-toanpv90
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: idea-refine
Source: https://github.com/ToanPV90/dotfiles/tree/main/claude/.claude/skills/idea-refine
Command: npx skills add https://github.com/ToanPV90/dotfiles --skill idea-refine-toanpv90

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

idea-refine helps you break out of incremental thinking by transforming a raw, vague concept into actionable directions you can evaluate and commit to.

Core Features & Use Cases

  • How Might We framing: Rewrites the raw idea into tension-filled problem statements that enable creativity and clarity.
  • Assumptions surfacing: Identifies what you’re presuming about users, success metrics, and constraints so you can validate the riskiest points.
  • Divergent to convergent workflow: Generates 5-8 distinct variations, clusters them into 2-3 directions, stress-tests each for user value, feasibility, and differentiation, and then sharpens toward execution via a one-pager.
  • Ruthless “Not Doing” list: Forces explicit scope boundaries so you don’t drift into sprawl.
  • User-approval gate: Ensures you don’t start building before the one-pager is approved by the target user.

Quick Start

Tell me the raw idea in one sentence and ask me to run idea-refine to produce 2-3 converged directions plus a one-pager with a “Not Doing” list and open questions.

Frequently Asked Questions about idea-refine

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn vague product ideas into actionable directions?

Refining vague product ideas involves rewriting them into tension-filled How Might We statements, surfacing assumptions, and generating 5-8 variations clustered into 2-3 directions stress-tested for user value and feasibility, resulting in an approved one-pager.

What is the best way to brainstorm when product requirements are unclear?

Brainstorming with unclear requirements requires framework-driven exploration that rewrites raw concepts into How Might We statements, surfaces hidden assumptions, and forces explicit scope boundaries via a ruthless Not Doing list before converging.

How do I break out of incremental thinking and explore distinct product variations?

Breaking out of incremental thinking requires generating 5-8 distinct variations, clustering them into 2-3 strategic directions, and stress-testing each for user value, feasibility, and differentiation to sharpen execution.

Does idea-refine work for creating a product one-pager with a Not Doing list?

Yes, idea-refine produces a user-approved one-pager that sharpens execution by defining explicit scope boundaries with a ruthless Not Doing list and highlighting open questions and riskiest assumptions for validation.

Can I use this approach to stress-test feature concepts for user value and feasibility?

Yes, you can stress-test feature concepts by evaluating clustered directions against user value, feasibility, and differentiation to ensure you commit to a shippable direction before building.

When should I not use framework-driven ideation for product strategy?

You should avoid framework-driven ideation if your requirements are already clear and defined, as the process specifically targets ambiguous concepts requiring divergent exploration before converging into a one-pager.