idea-refine

Transform raw ideas into actionable concepts through a structured three-phase ideation process.

3|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/nassimbf/ftitos-claude-code --skill idea-refine-nassimbf
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: idea-refine
Source: https://github.com/nassimbf/ftitos-claude-code/tree/main/skills/idea-refine
Command: npx skills add https://github.com/nassimbf/ftitos-claude-code --skill idea-refine-nassimbf

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Refines raw ideas into sharp, actionable concepts through a structured three-phase ideation process that moves ideas from exploration to a concrete plan.

Core Features & Use Cases

  • Phase-based ideation: Understand & Expand (Divergent), Evaluate & Converge (Convergent), Sharpen & Ship (artifact creation), delivering a Markdown one-pager that advances work.
  • Interactive guidance: Uses targeted questions and curated variations to surface assumptions and push thinking beyond initial ideas.
  • Output artifact: Produces a Markdown one-pager with problem framing, recommended direction, key assumptions, MVP scope, and a explicit Not Doing list to enforce focus, saved to docs/ideas/[idea-name].md.

Quick Start

Invoke the skill with an idea using /ideate [your idea] to begin a guided ideation session.

Frequently Asked Questions about idea-refine

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

FAQPage Schema
How do I refine raw ideas into actionable concepts using a structured framework?▼

To refine raw ideas into actionable concepts, use a three-phase ideation framework: Understand & Expand to explore divergent options, Evaluate & Converge to narrow down, and Sharpen & Ship to produce a concrete Markdown one-pager with an explicit Not Doing list.

What is the best way to document an MVP scope and surface hidden assumptions during ideation?▼

The best way to document an MVP scope and surface hidden assumptions is through interactive ideation guidance that asks targeted questions, ultimately generating a Markdown artifact containing problem framing, key assumptions, and a strict Not Doing list.

How do I structure a product or process-improvement ideation session from divergent exploration to a final plan?▼

Structure a product or process-improvement ideation session by progressing through three phases: divergent exploration to expand context, convergent evaluation to narrow focus, and artifact creation to ship a concrete one-pager output saved to your docs.

Does this ideation framework work for design and process-improvement contexts, or is it only for product development?▼

This ideation framework works across product, design, and process-improvement contexts. It applies a structured three-phase process to transform raw concepts into sharp, actionable plans regardless of the specific domain.

Can I generate a Markdown one-pager for my idea without manual formatting?▼

Yes, you can generate a Markdown one-pager automatically. The ideation process delivers a formatted artifact containing problem framing, recommended direction, MVP scope, and open questions, saving directly to docs/ideas/[idea-name].md.

Why include a Not Doing list when finalizing an idea or MVP scope?▼

Including a Not Doing list when finalizing an idea enforces focus by explicitly marking excluded features and assumptions. It ensures the MVP scope remains sharp and actionable within the generated Markdown one-pager.