idea-refine

Refine vague product ideas into decision-ready concept briefs with MVP boundaries and risks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Idea Refine converts a raw feature request or vague product direction into a small, decision-ready concept that clearly states the user problem, success signal, MVP boundary, risks, and next step—so teams avoid building without knowing what success means.

Core Features & Use Cases

  • Problem-to-concept reframing: Rewrites an idea into persona, job-to-be-done, obstacle, and impact without jumping straight to solution details.
  • MVP and scope convergence: Defines a smallest valuable MVP, explicit out-of-scope items, and deferred decisions to prevent scope creep.
  • Alternatives and risk posture: Produces at least two alternatives (e.g., do nothing vs smallest MVP) and lists risks with evidence needed to reduce uncertainty.
  • Workflow routing with confidence gating: Selects the next owning workflow (e.g., prd, requirements-intake, brainstorming) and blocks completion when confidence is too low, returning open questions instead.

Quick Start

Use the product idea you want to refine and ask the AI to run Idea Refine to produce a one-sentence concept brief, MVP boundary, risks, and the recommended next workflow step.

Frequently Asked Questions about idea-refine

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

FAQPage Schema
How do I turn a vague product idea into a decision-ready concept brief?

To turn a vague product idea into a decision-ready concept brief, you define the user problem, measurable success signals, constraints, MVP boundary, and risks to prevent building without clear success criteria.

What is the best way to define an MVP boundary and prevent scope creep for a new feature?

The best way to define an MVP boundary and prevent scope creep is by identifying the smallest valuable MVP, explicitly listing out-of-scope items, and deferring non-critical decisions during concept refinement.

How do I perform risk analysis and identify alternatives when refining a product strategy?

Performing risk analysis during product strategy refinement involves generating at least two alternatives like doing nothing versus building the smallest MVP, and listing specific risks alongside the evidence needed to reduce uncertainty.

Can I use confidence gating to block product requirements routing when evidence is incomplete?

Yes, you can use confidence gating to block workflow completion when evidence is incomplete, returning open questions instead of automatically routing the concept to PRD or requirements intake workflows.

When should I not use automated idea refinement for my feature request?

You should not use automated idea refinement when your feature request already contains a fully defined PRD with established success metrics, as this process targets vague directions needing convergence before implementation planning.