refine-idea

Convert fuzzy ideas into a bounded concept note through staged questioning.

Updated Jun 7, 2026
One-click install
npx skills add https://github.com/RollRollRoll/agent-toolkit --skill refine-idea
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: refine-idea
Source: https://github.com/RollRollRoll/agent-toolkit/tree/main/resources/skills/refine-idea
Command: npx skills add https://github.com/RollRollRoll/agent-toolkit --skill refine-idea

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps users convert fuzzy ideas into a bounded, executable concept without jumping into technical solutions, ensuring early clarity and reducing downstream rework.

Core Features & Use Cases

  • Identify real intent behind vague requests
  • Lock down what to do and what not to do
  • Stage-based questioning (Q+GUESS; multiple-choice boundaries) to surface uncertainties
  • Produce a lightweight concept document (concept-note) for later spec

Quick Start

Provide a scenario-based instruction: Start a session with a fuzzy idea and guide me through clarifying questions to produce a concept with defined boundaries.

Frequently Asked Questions about refine-idea

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

FAQPage Schema
How do I turn a fuzzy idea into a clear concept note without jumping into technical solutions?

To turn a fuzzy idea into a clear concept note, use a stage-based questioning process to surface uncertainties, identify real intent, and lock down what to do and what not to do. This prevents premature technical scoping.

What is the best way to scope vague ideas and define project boundaries early?

The best way to scope vague ideas is through a four-stage clarification process that targets real intent, audience, and timing. This method defines explicit boundaries to produce a lightweight, executable concept for later specification.

How do I clarify the true intent behind a vague product request before writing a specification?

You clarify true intent by applying multiple-choice boundaries and guided questioning techniques. This interactive scoping process exposes hidden uncertainties and separates the real demand from assumed needs before specification begins.

Does the ideation process require real-time human interaction to define boundaries?

Yes, the ideation process requires real-time human interaction to accurately surface uncertainties and define boundaries. This live engagement ensures the resulting concept note reflects true intent rather than automated assumptions.

Can I use this scoping process to produce a full technical implementation plan?

No, you cannot use this scoping process for technical implementation. It explicitly avoids action on implementation details, focusing instead on framing the concept and producing a lightweight note for later specification work.