discover

Convert vague ideas into shared clarity through adaptive conversational questioning.

14|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/hungv47/meta-skills --skill discover-hungv47
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: discover
Source: https://github.com/hungv47/meta-skills/tree/main/skills/meta/discover
Command: npx skills add https://github.com/hungv47/meta-skills --skill discover-hungv47

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conversational discovery closes the gap between what users say they want and what they actually need by turning vague ideas into shared clarity through adaptive questioning and alignment.

Core Features & Use Cases

  • Conversational scoping: adapt depth (Light / Medium / Deep) to the task and read context from existing artifacts.
  • Inline decisions or saved specs: produce immediate chat outcomes or a formal spec with a structured format.
  • Cross-skill routing: leverage plan-review vs idea-stage workflows and load appropriate procedural references for consistent results.

Quick Start

Describe your idea and let the agent set the depth, ask clarifying questions, and decide whether to save a spec.

Frequently Asked Questions about discover

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

FAQPage Schema
How do I turn vague project ideas into clear requirements?

Vague ideas become clear requirements through adaptive conversational scoping, where an agent asks targeted clarifying questions to establish shared alignment before work begins.

What is the best way to scope uncertain project requirements?

Scoping uncertain requirements works best through multi-round interviews that gather codebase context and apply depth auto-calibration, ensuring the final specification matches actual project needs.

Can I save a formal spec directly from a conversational alignment session?

Conversational alignment sessions can output formal saved specs with structured frontmatter and open branches, or produce immediate inline decisions depending on your workflow needs.

Do I need existing codebase artifacts to start a requirements discovery conversation?

Existing codebase artifacts are not strictly required but are highly valuable; the discovery process actively gathers context from artifacts to apply plan-review or idea-stage workflows accurately.

How many clarifying questions should I expect during requirements discovery?

Requirements discovery depth auto-calibrates based on task complexity, ranging from Light sessions with 3 to 5 questions to Deep multi-round interviews for comprehensive alignment.