vibeflow-discover

Name: vibeflow-discover
Availability: InStock
Author: pe-menezes

Guide interactive discovery dialogues to produce actionable Product Requirements Documents.

29|2|Updated Mar 3, 2026

Search Tags:#decision making #requirements gathering #idea refinement #scope definition #product discovery #prd generation

Ready to run

npx skills add https://github.com/pe-menezes/vibeflow --skill vibeflow-discover

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: vibeflow-discover
Source: https://github.com/pe-menezes/vibeflow/tree/main/cursor/skills/vibeflow-discover
Command: npx skills add https://github.com/pe-menezes/vibeflow --skill vibeflow-discover

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill transforms vague ideas into clear, actionable Product Requirements Documents (PRDs) by guiding users through a structured discovery dialogue, challenging assumptions, and forcing decisions to define scope.

Core Features & Use Cases

Interactive Dialogue: Engages in 1-5 rounds of questions and challenges to refine an idea.
Scope Definition: Aggressively cuts scope and defines explicit "anti-scope" to ensure a focused Minimum Viable Product (MVP).
Use Case: A product manager has a nascent idea for a new user onboarding flow. They use vibeflow-discover to hash out the core problem, target audience, and essential features, resulting in a well-defined PRD before moving to technical specification.

Quick Start

Use the vibeflow-discover skill to refine the idea of improving user onboarding.

Frequently Asked Questions about vibeflow-discover

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

FAQPage Schema

How do I turn a vague product idea into an actionable PRD?▼

Defining explicit anti-scope during product discovery prevents feature creep by establishing strict boundaries for the minimum viable product. It forces teams to intentionally exclude out-of-scope functionalities, ensuring development remains focused on solving the core problem.

Can I use project context files to inform the PRD generation process?▼

Yes, PRD generation can leverage project context from `.vibeflow/` files when available. This ensures the discovery process aligns with existing architecture patterns and technical constraints, producing requirements that fit seamlessly into your current system.

How many rounds of questions are needed to define a minimal viable product scope?▼

Defining a minimal viable product scope requires one to five rounds of interactive questioning. These rounds progressively refine the idea, challenge initial assumptions, and aggressively cut features until a focused MVP with explicit anti-scope is established.

What is the best way to refine requirements for a new user onboarding flow?▼

The best way to refine requirements for a user onboarding flow is through structured product discovery that hashes out the core problem and target audience. This interactive process results in a well-defined PRD before moving to technical specification.