clarify-idea

Clarify ambiguous user ideas through a structured conversational loop.

42|1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/kesteva/soloflow --skill clarify-idea
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clarify-idea
Source: https://github.com/kesteva/soloflow/tree/main/skills/clarify-idea
Command: npx skills add https://github.com/kesteva/soloflow --skill clarify-idea

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates wasted effort from working with unclear, half-formed user ideas by running a targeted clarification loop before structured extraction or task planning, ensuring all downstream steps have the context they need to deliver accurate results.

Core Features & Use Cases

  • Ambiguity Checklist: Automatically verifies if raw user input includes all required context (goal, target user, success signal, scope boundary, grounding) before proceeding.
  • Scope Decomposition Gate: Splits multi-part requests covering multiple independent subsystems into separate pieces so you clarify one deliverable at a time instead of juggling multiple ambiguous asks.
  • Guided Clarification Loop: Asks one focused, multiple-choice question at a time to resolve context gaps without overwhelming the user, with a mandatory readiness confirmation before moving to extraction.
  • Use Case: If a user submits a vague request like "I want to add a feature to my side project app", this Skill walks through clarifying the exact feature, target user, success criteria, and scope to produce a clear, actionable brief for downstream planning.

Quick Start

Invoke the clarify-idea skill whenever a user submits a vague product or feature request that is missing key context like goals, target users, or success criteria.

Frequently Asked Questions about clarify-idea

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

FAQPage Schema
How do I turn ambiguous feature requests into actionable product plans?▼

Ambiguous feature requests are transformed into actionable product plans through a guided clarification loop that verifies goals, target users, and scope boundaries via one multiple-choice question at a time before structured extraction.

What is the best way to resolve scope ambiguity in a vague product idea?▼

Resolving scope ambiguity in a vague product idea requires a scope decomposition gate that splits multi-part requests into separate pieces, allowing you to clarify one independent deliverable at a time instead of juggling multiple undefined asks.

How does requirement gathering work for half-formed user ideas?▼

Requirement gathering for half-formed user ideas works by applying an ambiguity checklist to detect missing context like success signals and grounding references, then prompting the user iteratively to fill those specific gaps.

Can I use this approach to clarify a bug report missing target user context?▼

Yes, you can clarify a bug report missing target user context because the process applies to free-form bug report inputs, checking for required context gaps and asking focused questions to disambiguate user intent before proceeding.

Does idea clarification require proposing implementation slices?▼

Idea clarification does not require proposing implementation slices; it strictly disambiguates user intent and confirms readiness, passing the clarified brief to downstream processing steps for actual task refinement.

Why does the clarification process ask only one question at a time?▼

The clarification process asks only one question at a time to resolve context gaps without overwhelming the user, ensuring a mandatory readiness confirmation gate is met before moving to structured extraction.