idea-refine

Refine raw ideas into actionable concepts with structured divergent and convergent thinking.

2|Updated May 3, 2026
One-click install
npx skills add https://github.com/Rosetears520/aili-workflows --skill idea-refine-rosetears520
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: idea-refine
Source: https://github.com/Rosetears520/aili-workflows/tree/main/skills/idea-refine
Command: npx skills add https://github.com/Rosetears520/aili-workflows --skill idea-refine-rosetears520

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you convert vague or early-stage ideas into clear, testable, build-ready concepts instead of endless ideation loops.

Core Features & Use Cases

  • Iterative Divergent/Convergent Refinement: Expands your idea with structured variations, then clusters and selects the most promising directions.
  • Assumption Surfacing and Stress-Testing: Forces explicit hidden assumptions, evaluates value/feasibility/differentiation, and challenges weak premises.
  • One-Pager Output for Moving Forward: Produces a concise markdown one-pager (problem, recommended direction, MVP scope, not-doing list, and open questions) suitable for next-step planning and validation.

Quick Start

Invoke the idea-refine skill with your raw concept and ask the agent to refine it into a build-ready one-pager.

Frequently Asked Questions about idea-refine

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

FAQPage Schema
How do I turn rough product ideas into build-ready concepts?

To turn rough ideas into build-ready concepts, apply structured divergent and convergent thinking to generate variations, cluster them into directions, and stress-test assumptions against user value and feasibility criteria.

What is the best way to frame a product problem for MVP planning?

The best way to frame a product problem for MVP planning is through interactive questioning that surfaces hidden assumptions, evaluates differentiation, and produces a concise markdown one-pager with a defined not-doing list.

How does assumption testing work during product ideation?

Assumption testing during product ideation works by explicitly surfacing hidden premises, stress-testing weak hypotheses against user value, feasibility, and differentiation, then challenging them before moving to MVP planning.

Can I use structured ideation to generate multiple product directions?

Yes, you can use structured ideation to generate 5-8 product variations, which are then clustered into 2-3 distinct directions to ensure you evaluate the most promising paths before committing to development.

What should be included in a one-pager for product validation?

A one-pager for product validation should include the defined problem, recommended direction, MVP scope, explicit not-doing list, surfaced assumptions, and open questions to guide next-step evaluation.

When do I need to stop ideating and start building an MVP?

You need to stop ideating and start building an MVP when you have a refined concept that has passed stress-testing for user value, feasibility, and differentiation, and is documented in an actionable one-pager.